oxidecomputer / oxidecomputer/omicron
System update status: transient `unknown` and `error` release versions are confusing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
While updating dogfood yesterday, I noticed some error codes would pop every now and then to later disappear without further explanation.
The update seemed to go through fine, yet I, as a user, would be doubtful it did if I saw errors without some acknowledgement of recovery or explanation of what or how critical they are.
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 locating the system update status handling and the code that presents release versions and transient error states. Reproduce or trace the status transitions described in the issue, then determine how recovery or criticality should be communicated. Done means users are not left with unexplained transient unknown or error versions after a successful update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100