oxidecomputer / oxidecomputer/humility
humility hiffy can be used to shoot yourself in the foot by sending an IPC to a task that hasn't been started
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
discovered by @jordanhendricks. if you use humility hiffy to send an IPC to a task that is not configured to start automatically and has not been started explicitly, it just hangs. this puts the hiffy task in a state where it seems to be stuck forever unless restarted. whoops.
this seems not great. it would be nice if humility could check that the task you want to talk to is running and warn you if you're about to shoot yourself in the foot. implementing that might be a little annoying but it seems plausible...
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 hiffy entry point and reproduce an IPC sent to a task that is not configured to start automatically and has not been started. Trace how the command handles that target, then verify that it warns instead of hanging and leaving the hiffy task stuck.
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
- 35/100