oxidecomputer / oxidecomputer/humility
Humility does not deal with disabled ringbuf properly
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
Running humility ringbuf against a hubris that contains a disabled ringbuf results in the ringbuf dump stopping on the disabled ringbuf.
Cargo.toml:
...
[dependencies]
...
ringbuf = {path = "../../lib/ringbuf", features = ["disabled"]}
#ringbuf = {path = "../../lib/ringbuf"}
...
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
Reproduce the issue with humility ringbuf against a Hubris configuration using the ringbuf disabled feature shown in Cargo.toml. Trace the ringbuf command's handling of that configuration; done means the dump continues past a disabled ringbuf instead of stopping there.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100