yakut reg produces wrong format on output for natural8 with option -d
Open
Nobody has claimed this yet.
blocked
- Dominant language
- Python
- Stars
- 65
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
yakut reg produces wrong format on output for natural8 with option -d
bernhard@notebookR60P-22:~$ y -i 'CAN(can.media.socketcan.SocketCANMedia("slcan0",8),59)' r 42 uavcan.node.id
11
bernhard@notebookR60P-22:~$ y -i 'CAN(can.media.socketcan.SocketCANMedia("slcan0",8),59)' r -d 42 uavcan.node.id
natural8: {value: "\v"}
bernhard@notebookR60P-22:~$ y --version
yakut, version 0.11.1
Contributor guide
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
Re-run the reported yakut reg commands with and without -d against uavcan.node.id to confirm the natural8 formatting difference. Start at the yakut reg command entry point and trace its detailed-output formatter; done means the natural8 value is rendered consistently with the expected register output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100