Allow debug messages to be sent to stdout #255
Closed
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
|
+1 |
|
I also need this... +1 |
I think that's because the debug level used to be higher. The fact that debug still goes to stderr seems like a bug to me. Oh, and 👍 |
|
Hello hello? +1 |
|
+1 |
|
+1 On Fri, Aug 8, 2014 at 12:02 PM, Wes Todd [email protected] wrote:
|
|
I don't really see the need for this, but since enough people want it we will put it into |
|
great! |
|
+1 |
|
Cherry-picked. Thanks! |
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.
Currently debug messages for console transport always go to stderr.
This change introduces a new option called "debugStdout" which defaults to false (so console is backward compatible). If set to true, debug messages will go to stdout instead of stderr.
Just curious - but why are debug messages going to stderr by default?