oxidecomputer / oxidecomputer/sush
State machine is a mess
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 11
Description
The current implementation of the state machine has grown overly complex and fragile. It is also essentially impossible to test in isolation. Related mechanisms like the execution boundary and universe flip-flop handling have similar concerns; see comments on #71. A rewrite is needed at this point.
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
Start by reading the current state-machine implementation and the comments on issue #71. Identify how the execution boundary and universe flip-flop handling relate to the state machine, then determine the scope of the rewrite. Done should include a simpler design that can be tested in isolation and addresses the related concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100