oxidecomputer / oxidecomputer/crucible
Upstairs should re-verify generation number when a downstairs reconnects
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 260
- Forks
- 34
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 8
Description
When an active downstairs goes away then comes back, the upstairs should re-verify the max generation number from that
downstairs matches what it has and refuse to reconnect if it's not.
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
Trace the upstairs/downstairs reconnect handling and the exchange of the maximum generation number. Verify the existing behavior for matching and mismatching generations; done means a matching downstairs can reconnect while a mismatched one is refused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100