rigetti / rigetti/qcs-sdk-rust
QPU-Specific Diagnostics
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
Today, we have a diagnostics utility within the SDK that's useful for identifying certain common misconfigurations and user errors.
What's missing are diagnostics relating to execution and results retrieval. These will help users to independently identify and perhaps resolve issues related to network access and authorization for certain QPUs. This should include, for a user-specified QPU ID:
- Can the ISA and calibration program be retrieved?
- Are the direct access endpoint and all accessors reachable and healthy?
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 locating the SDK's existing diagnostics utility and the APIs used to retrieve a user-specified QPU's ISA, calibration program, direct access endpoint, and accessors. Determine how reachability and authorization are currently represented. Done means diagnostics report whether each requested resource can be retrieved and each endpoint or accessor is reachable and healthy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- authentication, backend-api-design, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100