Join GitHub today
'debug' level is getting directed to stderr instead of stdout #927
Found the answer here:
... i.e. setting the levels to log to stderr instead of stdout via
FWIW, I didn't find it very intuitive that this option would default to
I'll let someone on the project close this issue after reading this feedback, but I need no additional help.
Maybe I can see the sense of it, although I do not agree with it.
It might make sense under the following terms:
In this case, you'll have to search for your debug notices in the file/sql/loglly,
IMHO - It's a kinda twisted gotcha. I'm here just because I ran into it myself, and decided to share my observation.
It's of the kind of settings that are fit to development time, and nowhere else.
I agree that this is a very strange default setting.
I'm building a system that runs commands locally, and it also runs its own commands over SSH in child processes too. And have been investigating why the local commands appeared to work (I'm not monitoring STDERR on the main local node process), but the same remote SSH commands were producing STDERR output (I'm throwing local exceptions when the child process's remote command has STDERR output).
First I thought it was something to do with SSH itself handling output differently until I ran further tests to rule SSH out, and after a while thought to look into Winston.
Thanks for posting this issue. This would have taken me a while longer to figure out otherwise.