Extension crash with latest VSCode Update

[m-code-official]

Describe the bug A clear and concise description of what the bug is.

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. See error

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Mac, Win, Linux]
• VSCode Version [e.g. 1.27.0]
• Extension Version [e.g. 1.7.0]

Extension Logs - required You can get the logs from View > Output > remote-fs.

[jakelishman]

This is a question that's beyond the scope of base Qiskit's interfaces, but would be special-case access that certain backends might be able to provide, based on how they function underneath. Exposing the raw data can sometimes be very expensive in terms of data transfer for backends, which might explain why people want to drop support for it.

For IBM backends in particular, you might want to look at what options are available to you through the V2 primitives for IBM hardware, which may give you what you need - the exact details are a bit outside my wheelhouse sorry. Beyond that, you'll probably be better off asking on https://github.com/Qiskit/qiskit-ibm-runtime, which is the repository for the frontend to the IBM hardware.

[ihincks]

I'm not familiar with this feature. What format would this timing information be specified in, and what exactly is it timing? Like a timestamp for each shot?

[alan23273850]

My timing means the total running time of a quantum circuit in each shot. I've participated in some talk where the speaker claims that if this information can be printed, then it would be very helpful to his research. Is it possible for IBM backends? Thanks again!

[jyu00]

Exactly what kind of per-shot running time are you looking for? If it's just gate time (i.e. time needed to process all the gates), then you can already calculate that number using the gate & readout lengths from backend properties. If you want to start the timing from when the quantum program is loaded into control electronics, then there isn't really a "per shot" time since some operations (like load) only happens once.

By the way, in case it wasn't obvious, SamplerV2 already gives you per shot measurement (similar to the old memory=True).

[jyu00]

Closing since there doesn't seem to be further questions.