oxidecomputer / oxidecomputer/omicron
Nexus should fail more loudly when the populate step fails
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
See #5980. When the populate step fails, Nexus could be in an arbitrarily broken state (imagine: its internal identities may not be authorized to do anything at all). Right now Nexus just logs an error when this happens because we don't have a better way to flag serious problems (aside from crashing). It'd be great if we could log a high-severity "active problem" or alert or something.
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
Start by reading issue #5980 and tracing how Nexus handles and logs failures from the populate step. Determine what high-severity signal or active-problem mechanism the project supports, then verify that a populate failure produces an observable alert rather than only a log message.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100