[BUG] YAML configuration option rx 'hardware_timestamps' not parsed
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 36
- Forks
- 11
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 25
Description
Describe the bug
The 'hardware_timestamps' field is accidentally not parsed when reading in a DAQIRI config YAML
Steps/Code to reproduce bug
Put 'hardware_timestamps' field set to true in a DAQIRI config yaml, run a test and see that the in memory configuration has it set to the default false.
Expected behavior
YAML config processing should parse the 'hardware_timestamps' field.
Environment overview (tested on this environment but expected in all environments)
- Environment location: Docker
- Method of DAQIRI install: source
Environment details
Tested on this environment but expected in all environments:
- OS and version: Ubuntu 24.04
- Python version: 3.12
- DAQIRI version: 57f3d8ebdd2e5410f654edea2e25b211cbca17de
- Hardware configuration: x86 and GH200 with BF3
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
Search the DAQIRI YAML configuration processing for the existing hardware_timestamps field and compare it with neighboring fields that are parsed. Reproduce the issue using a configuration with hardware_timestamps set to true, then verify that the in-memory configuration retains true instead of the default false.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, yaml
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100