rigetti / rigetti/qcs-sdk-rust
Client-side accessor preferences
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
Related to https://github.com/rigetti/qcs-sdk-rust/pull/573
When selecting the best Accessor gRPC URL, the client should consider all possible Accessors of the target type (e.g. "gateway") and do a latency check in order to determine the best one to connection.
Separately, if a higher-preference Accessor cannot be connected to, subsequent options should be attempted. This will be important if the highest-priority Accessor does not allow ingress from a particular client.
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 by reviewing pull request #573 and the existing client-side Accessor selection and connection logic. Determine how all Accessors of the target type are discovered and prioritized; the work is done when latency informs selection and connection failures fall back to subsequent options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100