oxidecomputer / oxidecomputer/crucible
Error handling cleanup
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
Perform a code walkthrough and determine what happens on errors.
Report errors back to Nexus.
Make sure we are using unwrap/? correctly. We should never panic the upstairs/downstairs
on situations where we could handle the error gracefully.
Contributor guide
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 a repository-wide walkthrough of Rust error paths, focusing on uses of unwrap and ?. Trace how errors currently propagate and whether Nexus receives them. Done means the findings are addressed so errors that can be handled gracefully are reported to Nexus without panicking the upstairs or downstairs components.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100