oxidecomputer / oxidecomputer/humility
Consider removing timeouts on hiffy commands.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
(This is mostly about the spi command but I think it's worth considering as a general principle.)
The default timeout on humility spi keeps tripping people up. I suggest that timeouts on hiffy commands in general might be a bad idea.
- Hiffy commands are often run interactively, where the user can ^C if they're tired of waiting or think it's wedged.
- Any default timeout will inherently run up against Clulow's Law.
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 with the humility spi command and trace the general timeout path for hiffy commands. Reproduce the default timeout behavior described in the issue, then establish and verify the intended policy for interactive commands, including user interruption.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100