oxidecomputer / oxidecomputer/humility
`humility dump --print-dump-breakdown` is confusing
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
While looking at https://github.com/oxidecomputer/hubris/issues/2031 , folks ran humility dump --print-dump-breakdown.
This reinitialized the system's dump state, overwriting previous data, which was surprising given the name. We should probably not do that!
Contributor guide
No contributing guide indexed for this repository
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 at the humility dump --print-dump-breakdown command entry point and reproduce the behavior described in this issue, referring to Hubris issue 2031 for context. Done means printing the dump breakdown no longer reinitializes or overwrites the system's existing dump state.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100