With a raised log level, logs are written to stdout

Open Beginner friendly
#108 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
rust
Domain
cli

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.

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.

Dominant language
Rust
Stars
782
Forks
52
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from n0-computer/dumbpipe

All issues in n0-computer/dumbpipe

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.