feat(output): redirect trace output to stderr #1084
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allow trace output with any non-standard output format by writing trace to stderr while maintaining formatted output on stdout. This enables using `--trace` with table, JSON, etc. formats. Currently, when using `--trace` with any non-standard output format, no traces are shown at all. The new behavior actually adds functionality by showing traces in stderr while maintaining the formatted output in stdout. Scenarios where non-standard output is piped to another process will continue to work without breaking changes. For the default output format (stdout), traces still go to stdout for backwards compatibility. Signed-off-by: Ville Vesilehto <[email protected]>
thevilledev
force-pushed
the
feat/trace-stderr
branch
from
2fdf368 to
dd9c470
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allow trace output with any non-standard output format by writing trace to stderr while maintaining formatted output on stdout. This enables using
--tracewith table, JSON, etc. formats.Currently, when using
--tracewith any non-standard output format, no traces are shown at all. The new behavior actually adds functionality by showing traces in stderr while maintaining the formatted output in stdout. Scenarios where non-standard output is piped to another process will continue to work without breaking changes.For the default output format (stdout), traces still go to stdout for backwards compatibility.
Fixes #1031