Skip to content

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

@BatmanAoD

Description

@BatmanAoD

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions