You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should the target also not be cached when calling target_history()? Currently, calling backend.target after backend.target_history() would still return the old target.
Should the target also not be cached when calling target_history()? Currently, calling backend.target after backend.target_history() would still return the old target.
Right. Backend properties should not be cached if an older copy is requested.
Describe the bug
backend.target_history()
calls_get_properties()
:qiskit-ibm-runtime/qiskit_ibm_runtime/ibm_backend.py
Lines 349 to 355 in 51d897b
which saves the properties of that given timestamp as
_properties
:qiskit-ibm-runtime/qiskit_ibm_runtime/ibm_backend.py
Lines 241 to 249 in 51d897b
which means if I do
I'll actually get
old_history
back in my second call.Steps to reproduce
Expected behavior
Historical properties should not be cached.
backend.properties()
does this correctly.Suggested solutions
Don't cache properties if datetime is provided.
Additional Information
The text was updated successfully, but these errors were encountered: