oxidecomputer / oxidecomputer/hubris
Any changes needed in-tree to support future IPCC debugging?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.6k
- Forks
- 239
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 23
Description
@rmustacc mentioned that @jgallagher and @citrus-it wound up needing a bunch of bespoke SP changes to debug IPCC behavior recently, and asked if there's any subset of that that we should pull into the main tree.
That sounds like a good idea, so this issue is a placeholder.
@jgallagher / @citrus-it - thoughts?
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 collecting the bespoke SP changes used by @jgallagher and @citrus-it for recent IPCC debugging, then compare them with the main tree. Determine which subset is broadly useful and define the expected debugging workflow before proposing an implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- embedded-iot, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100