oxidecomputer / oxidecomputer/crucible
crucible-downstairs should retry when creating a clone
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
If we are creating a clone from another downstairs, we should retry if the initial connection attempt fails.
We could be in a race with the other side, or there could be some temporary issue (sled reboot) and things
might come back.
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
No file or test is named. Start by locating the crucible-downstairs clone-creation path and its initial connection handling, then inspect how transient connection failures are reported. Done means a failed initial connection is retried so races or temporary sled reboots can recover.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100