Andres Paz

@jond01, I think the context that you're missing here is that we don't send the Q# code to the service but it actually needs to be compiled into QIR or...

@guenp Adding support for job batching is a great idea, and it's on our road-map, but to be perfectly clear it is **not** a pre-requisite for qiskit-experiments, QAOA or VQE....

Looks like Qiskit is expecting the configuration of all backends to extend [BackendConfiguration](https://qiskit-test.readthedocs.io/en/latest/api/qiskit.providers.models.BackendConfiguration.html#qiskit.providers.models.BackendConfiguration) to report the required configuration settings. Our backends should do the same. Similarly, our backends should also...

I took a closer look to our Backends, and they are already using `BackendConfiguration`, even more, the configuration already includes `memory`, for example, [here](https://github.com/microsoft/qdk-python/blob/b75676967a952763bd565b84ddc983de8d25809d/azure-quantum/azure/quantum/qiskit/backends/ionq.py#L141) and [here](https://github.com/microsoft/qdk-python/blob/b75676967a952763bd565b84ddc983de8d25809d/azure-quantum/azure/quantum/qiskit/backends/quantinuum.py#L185). Since `memory` is not...

Yes, unfortunately this is not currently supported by any of our backends. We are working towards supporting the ability to log intermediate results, which will enable the scenario you are...

Unfortunately, I'm seeing the same problem when using the aio library. There seems to be some deadlock happening on a low-level http library. I have opened a ticket with the...

More analysis suggests this is a service problem, which we're investigating and might have a solution soon.

this has been merged already.

/azp run

This should be fixed with #708, which is now released as part of the QDK 0.25.228311+