Skip to content
This repository has been archived by the owner on Jul 28, 2023. It is now read-only.

The old provider is stuck on the way back from the device to my console #1174

Open
yaelbh opened this issue May 22, 2023 · 2 comments
Open
Labels
type: bug Something isn't working

Comments

@yaelbh
Copy link

yaelbh commented May 22, 2023

It's important for me to still use the old provider because of bugs with the new provider, using pulses. I'll try to create small examples and open separate issues.

When I run a simple circuit on the old provider:

from qiskit import QuantumCircuit, IBMQ

IBMQ.load_account()

provider = IBMQ.get_provider(<details>)
backend = provider.backend.<backend name>

circ = QuantumCircuit(1, 1)
circ.x(0)
circ.measure(0, 0)

res = backend.run(circ).result()
print(res.get_counts(0))

I can see on the IQX page that the job completed successfully. But my console gets stuck and never reaches the print line.

With the new provider it works fine.

@yaelbh yaelbh added the type: bug Something isn't working label May 22, 2023
@kt474
Copy link
Member

kt474 commented May 22, 2023

Most backends/providers have been migrated to use runtime. It's not possible to retrieve runtime jobs from the old provider.

It gets stuck because it's trying to use the old IQX api to retrieve a runtime job that would only be retrievable with the runtime api.

@yaelbh
Copy link
Author

yaelbh commented May 22, 2023

Since the old provider is only deprecated, and not totally disabled, it should probably work for all backends and providers in this point of time.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants