oxidecomputer / oxidecomputer/humility
humility network error messages could provide more context
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
I was trying to run capture a dump from an SP that is broadcasting, but not accepting comms:
rm@jeeves ~ $ pfexec humility -i fe80::aa40:25ff:fe04:346%e1000g0 -a /net/catacomb/data/staff/dock/rack2/gimlet/c/sp/gimlet-c-perst-spec-viol.zip dump
humility: connecting to fe80::aa40:25ff:fe04:346%e1000g0
humility dump failed: Resource temporarily unavailable (os error 11)
From the output of truss this is a call to recv getting EAGAIN:
send(3, " = wAE %DA889B Q17\001\0".., 21, 0) = 21
recv(3, 0xFFFFFC7FFFDFBFC0, 1024, 0) (sleeping...)
recv(3, 0xFFFFFC7FFFDFBFC0, 1024, 0) Err#11 EAGAIN
Having the context that it was the network would have sped this up
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
Run the shown humility ... dump command first and trace the recv failure returning EAGAIN in the network path. Done means the humility dump error identifies that the failure came from the network and provides useful context; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100