rigetti / rigetti/qcs-sdk-rust
Detect and handle when gRPC get-results timeout is shorter than ConServ's estimated job duration
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
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
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the gRPC EstimatedDelay API and trace the SDK's job submission and get-results flows. Determine where job status is requested and how cancellation or a longer results timeout can be exposed; done means users can detect an insufficient timeout and either cancel or retry with a sufficient one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100