oxidecomputer / oxidecomputer/omicron
wicket: Don't offer to start updates on components that aren't present
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 572
- Forks
- 97
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 96
Description
wicket refuses to allow the operator to update the scrimlet and switch by which they are connected; however, it will allow them to (attempt to) start an update on components that are not physically present. wicket already knows which devices are present (via both ignition presence and failure to communicate with the SP); if the target isn't present, it shouldn't offer to start an update.
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 tracing wicket's update-start decision path and how it determines component presence from ignition presence and failed communication with the SP. Reproduce the case for an absent target, then verify that wicket no longer offers an update while still allowing present components to proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100