oxidecomputer / oxidecomputer/sush
When first joining gossip, we should read to the end *before* we start executing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
This is so that we can ensure that we only execute jobs from the most recent session, and only if that session is not yet ended. We need a way to scan through all the messages and load them into the state machine without dispatching any jobs, then only once we've processed them, go back and start actually taking actions for only the most recent session. Otherwise, if you missed a session end and are catching up, you'll run jobs you shouldn't.
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. Start by locating the gossip message-processing and state-machine code, then trace session-end handling and job dispatch. Done means catch-up loads all messages without dispatching, and only jobs from the latest unfinished session are executed.
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
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100