oxidecomputer / oxidecomputer/hubris
Should `Uncontrollable` thermal state be terminal?
Open
Nobody has claimed this yet.
thermal 🚫🔥🚫
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
10 780 3 1 ControlPwm(0x63)
11 780 3 242 ControlPwm(0x64)
12 700 3 1 AutoState(Overheated)
13 780 3 61 ControlPwm(0x64)
14 767 3 1 AutoState(Uncontrollable)
15 562 3 1 PowerModeChanged(0x1)
16 516 3 1 AutoState(Boot)
17 660 3 1 AutoState(Running)
18 780 3 184 ControlPwm(0x0)
It's surprising to me that the system dropped back into Running after powering itself off.
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 with the event trace in the issue, focusing on AutoState(Uncontrollable) and the subsequent PowerModeChanged, Boot, and Running events. Determine whether Uncontrollable is intended to be terminal and what behavior should follow; done means the intended transition is established and the observed return to Running is resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100