oxidecomputer / oxidecomputer/hubris
It would be useful to know the RoT's uptime.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
We don't currently have a way to ask the RoT how long it's been running. Knowing this would be useful to distinguish "the SP reset" from "the whole board lost power."
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
No file, test, or entry point is named. Start by locating the RoT request interface and existing status or diagnostic responses, then determine how uptime should be exposed and what distinguishes a service-processor reset from a board power loss. Done means the RoT reports its running duration through a documented, test-covered interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100