rigetti / rigetti/qcs-sdk-rust
Expose error model to both Rust and Python users
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
There will be new error metadata in the Rigetti gRPC API; once available, this SDK should provide access to that metadata for all clients.
In Rust, distinct errors should be represented as enum variants (though they do not necessarily all need to be part of the same enum). We should additionally keep the existing variants for errors that are not part of the API, such as failure to establish a gRPC connection at all.
In Python, distinct errors should be represented as different Python Exception classes, corresponding 1:1 with the Rust enum variants.
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
No files, tests, or entry points are named. First inspect the SDK's existing Rust error variants and Python exception classes, then review the Rigetti gRPC API's new error metadata when it is available. Done means API errors are exposed as corresponding distinct Rust variants and Python exception classes while non-API failures remain represented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100