oxidecomputer / oxidecomputer/crucible
BlockReq error handling when send fails
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
It'd have to flow through something else, if we can't send anything through the Sender here. maybe this deserves a followup issue
Originally posted by @jmpesp in https://github.com/oxidecomputer/crucible/pull/449#discussion_r977828320
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 by tracing BlockReq handling and the Sender path described in the issue, focusing on what happens when sending fails. Determine how the failure should flow through another path or be handled as a follow-up, then verify that the chosen error path is exercised.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100