We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug
The refresh() method in FakeBackendV2 only refreshes if the backend configuration changes:
refresh()
FakeBackendV2
qiskit-ibm-runtime/qiskit_ibm_runtime/fake_provider/fake_backend.py
Line 600 in 2e969ff
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:
Lines 593 to 595 in 2e969ff
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
The text was updated successfully, but these errors were encountered:
kt474
Successfully merging a pull request may close this issue.
Describe the bug
The
refresh()
method inFakeBackendV2
only refreshes if the backend configuration changes:qiskit-ibm-runtime/qiskit_ibm_runtime/fake_provider/fake_backend.py
Line 600 in 2e969ff
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:
qiskit-ibm-runtime/qiskit_ibm_runtime/fake_provider/fake_backend.py
Lines 593 to 595 in 2e969ff
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
The text was updated successfully, but these errors were encountered: