Skip to content
New issue

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

FakeBackend.refresh() doesn't always refresh #1993

Open
jyu00 opened this issue Oct 24, 2024 · 0 comments · May be fixed by #2020
Open

FakeBackend.refresh() doesn't always refresh #1993

jyu00 opened this issue Oct 24, 2024 · 0 comments · May be fixed by #2020
Assignees
Labels
bug Something isn't working
Milestone

Comments

@jyu00
Copy link
Collaborator

jyu00 commented Oct 24, 2024

Describe the bug

The refresh() method in FakeBackendV2 only refreshes if the backend configuration changes:

if updated_config != self._conf_dict:

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:

real_props = real_backend.properties()
real_config = real_backend.configuration()
real_defs = real_backend.defaults()

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

  • qiskit-ibm-runtime version:
  • Python version:
  • Operating system:
@jyu00 jyu00 added the bug Something isn't working label Oct 24, 2024
@kt474 kt474 self-assigned this Nov 6, 2024
@kt474 kt474 linked a pull request Nov 6, 2024 that will close this issue
@kt474 kt474 added this to the 0.34.0 milestone Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants