Timestamp / count don't always catch newlines? :(
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44
- Forks
- 59
- Avg merge
- 20h 33m
- Merged PRs (30d)
- 2
Description
Posting for later investigation, but a device printing like this:
printf("\r");
for (j=0; j<adv.dlen; j++) {
printf("%02x", adv.data[j]);
}
printf("\n");
doesn't result in the timestamp / count option working, which is a bit surprising as I'd expect that lone '\n' at the end to make things happy
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
No source file, test, or entry point is named. Reproduce the behavior using the shown output pattern, then trace how timestamp and count options detect record boundaries and newline characters. Done means newline-terminated output is handled consistently by both options and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100