oxidecomputer / oxidecomputer/hubris
gimlet: sequencer should notice MAPO faults
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
This may or may not be true of the Sidecar and/or psc as well, but often times we hit the case where we say thermtrip or something else happens and the sequencer changes the power state, but the SP doesn't notice this. This likely wants us to get sequencer interrupts (not sure if they're there yet @nathanaelhuffman) and to get the sequencer tasks notified and able to take action based on this so its sense of the power state isn't out of date.
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 gimlet sequencer, its interrupt support, and the sequencer tasks referenced in the issue; check whether MAPO or other fault notifications already have an entry point. Clarify how the SP should learn about a sequencer-driven power-state change, then verify that its recorded power state stays current after a thermtrip or similar fault.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100