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

Detect and handle when gRPC get-results timeout is shorter than ConServ's estimated job duration #492

Open
BatmanAoD opened this issue Aug 10, 2024 · 0 comments

Comments

@BatmanAoD
Copy link
Contributor

The gRPC API now has a way to get the "estimated delay" before a job will be complete: https://docs.api.qcs.rigetti.com/protobuf/#services.controller.EstimatedDelay

When the minimum delay is greater than the get-results gRPC timeout, the client will not be able to get the job results.

The SDK should automatically detect this situation (by requesting the job status either immediately after submitting a job, or automatically as part of requesting the job results), and it should permit the user to do either of the following:

  • cancel the job
  • re-request results with a sufficiently long timeout
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant