oxidecomputer / oxidecomputer/hubris
Need better way to distinguish intended host state from current state
@evan-oxide is already working on this.
Since May 5, 2026.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
I was debugging some cases earlier today where some sleds appear to have been rebooting. I appear to have caught a case where the sled was briefly in A2. I got this via pilot sp status, which is using faux-mgs to understand the current power state. However, the thing that I didn't know was that this was probably in the process of rebooting due to a host boot / panic loop. We need some way to better distinguish what is the current power state from what is happening or transient. In general when I see us in A2, I assume we have come to rest in A2 not that we're in the process of making a transition. Perhaps there's some additional set of APIs or way we can expose this. I'm not sure what makes the most sense or how we want to denote intent versus reality.
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.
Assessment
This issue has not been assessed yet.