n0-computer / n0-computer/dumbpipe
With a raised log level, logs are written to stdout
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 782
- Forks
- 52
- PR merge metrics
- No merged PRs in 30d
Description
The root of this problem is that tracing-subscriber sends logs to stdout.
The peer's stream goes to stdout so messages should go to stderr, to not clobber the transmitted file.
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
Search the logging setup for the tracing-subscriber configuration and inspect how the peer stream uses stdout. Verify that logs are directed to stderr while transmitted file data remains on stdout, then run the existing tests or a pipe transfer to confirm the output is not clobbered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100