oxidecomputer / oxidecomputer/humility
`sensors` maybe doesn't understand `other_sensors`?
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 584
- Forks
- 63
- Avg merge
- 3h
- Merged PRs (30d)
- 2
Description
$ pfexec ./humility sensors -d qsfp
humility: attached to 483:3754:0039001D4741500920383733 via ST-Link V3
humility sensors failed: unrecognized device qsfp
Is this because it is an other_sensors?
But it will gladly return them all time otherwise, e.g.,
aaron@sam ~ $ pfexec ./humility sensors -d raa229618
humility: attached to 483:3754:0039001D4741500920383733 via ST-Link V3
NAME KIND VALUE UNPWR ERR MSSNG UNAVL TMOUT
V0P8_TF2_VDD_CORE temp - 63+ 0 0 0 0
V0P8_TF2_VDD_CORE current - 63+ 0 0 0 0
V0P8_TF2_VDD_CORE voltage - 63+ 0 0 0 0
V0P9_TF2_VDDT temp - 63+ 0 0 0 0
V1P5_TF2_VDDA temp - 63+ 0 0 0 0
V0P9_TF2_VDDT current - 63+ 0 0 0 0
V1P5_TF2_VDDA current - 63+ 0 0 0 0
V0P9_TF2_VDDT voltage - 63+ 0 0 0 0
V1P5_TF2_VDDA voltage - 63+ 0 0 0 0
xcvr0 temp - 0 0 0 0 0
xcvr1 temp - 0 0 0 0 0
xcvr2 temp - 0 0 0 0 0
xcvr3 temp - 0 0 0 0 0
xcvr4 temp - 0 0 0 0 0
xcvr5 temp - 0 0 0 0 0
xcvr6 temp - 0 0 0 0 0
xcvr7 temp - 0 0 0 0 0
xcvr8 temp - 0 0 0 0 0
xcvr9 temp - 0 0 0 0 0
xcvr10 temp - 0 0 0 0 0
xcvr11 temp - 0 0 0 0 0
xcvr12 temp - 0 0 0 0 0
xcvr13 temp - 0 0 0 0 0
xcvr14 temp - 0 0 0 0 0
xcvr15 temp - 0 0 0 0 0
xcvr16 temp - 0 0 0 0 0
xcvr17 temp - 0 0 0 0 0
xcvr18 temp - 0 0 0 0 0
xcvr19 temp - 0 0 0 0 0
xcvr20 temp - 0 0 0 0 0
xcvr21 temp - 0 0 0 0 0
xcvr22 temp - 0 0 0 0 0
xcvr23 temp - 0 0 0 0 0
xcvr24 temp - 0 0 0 0 0
xcvr25 temp - 0 0 0 0 0
xcvr26 temp - 0 0 0 0 0
xcvr27 temp - 0 0 0 0 0
xcvr28 temp - 0 0 0 0 0
xcvr29 temp - 0 0 0 0 0
xcvr30 temp - 0 0 0 0 0
xcvr31 temp - 0 0 0 0 0
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 sensors command and the other_sensors definition in drv/transceivers-api/src/lib.rs. Trace how -d device names are matched, then verify behavior with the shown qsfp and raa229618 invocations. Done means qsfp can be selected appropriately or the command clearly reports why it cannot.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, embedded-iot
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100