Open mcandre opened 1 year ago
@mcandre Thanks for filing this issue! Do you happen to remember what exactly did you not expect to appear in stdout
?
Your observations are quite important for #3803 as I'm planning to move the whole logging system to tracing
(it currently targets stderr
exclusively) and I do want to get more insights into the original implementation and its issues. Thanks!
Problem
When rustup emits error messages, these sometimes appear on the stdout stream, instead of the stderr stream. This makes it harder for aggregate CLI commands to distinguish between logs (such as lists of target triples) vs. error messages.
Steps
rustup target list foo
with and without redirecting stdout to a null stream.Possible Solution(s)
Ensure that all error messages write to the stderr stream, rather than stdout.
Notes
No response
Rustup version
Installed toolchains