oxidecomputer / oxidecomputer/omicron
fm: Active Problem rendezvous
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
Once both #11037 and #11039 are complete, we will need to actually tie together the sitrep's view of the set of Active Problems with the rest of the world's view in the rendezvous process. This means editing the current state of active problems as visible to the HTTP API and other subsystems based on the state in the current sitrep.
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
First review the completion and interfaces of #11037 and #11039, then trace the rendezvous process and the current sitrep representation of Active Problems. Identify how the HTTP API and other subsystems read the active-problem state; done means those views are updated from the current sitrep during rendezvous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100