Open jyu00 opened 1 month ago
Describe the bug
The refresh() method in FakeBackendV2 only refreshes if the backend configuration changes:
refresh()
FakeBackendV2
https://github.com/Qiskit/qiskit-ibm-runtime/blob/2e969ffc11eec7d8a1c283998272f630f913cf55/qiskit_ibm_runtime/fake_provider/fake_backend.py#L600
But there is a high chance backend properties/defaults would change even if configuration stays the same.
In addition, it uses the cached objects even when updates are made:
https://github.com/Qiskit/qiskit-ibm-runtime/blob/2e969ffc11eec7d8a1c283998272f630f913cf55/qiskit_ibm_runtime/fake_provider/fake_backend.py#L593-L595
But one would expect refresh() to fetch the latest and greatest.
Steps to reproduce
Expected behavior
Suggested solutions
This refresh() should always fetch/store the latest server data.
Additional Information
Describe the bug
The
refresh()
method inFakeBackendV2
only refreshes if the backend configuration changes:https://github.com/Qiskit/qiskit-ibm-runtime/blob/2e969ffc11eec7d8a1c283998272f630f913cf55/qiskit_ibm_runtime/fake_provider/fake_backend.py#L600
But there is a high chance backend properties/defaults would change even if configuration stays the same.
In addition, it uses the cached objects even when updates are made:
https://github.com/Qiskit/qiskit-ibm-runtime/blob/2e969ffc11eec7d8a1c283998272f630f913cf55/qiskit_ibm_runtime/fake_provider/fake_backend.py#L593-L595
But one would expect
refresh()
to fetch the latest and greatest.Steps to reproduce
Expected behavior
Suggested solutions
This
refresh()
should always fetch/store the latest server data.Additional Information