debug icon indicating copy to clipboard operation
debug copied to clipboard

not getting any output

Open twhitbeck opened this issue 4 years ago • 3 comments

We upgraded to 4.3.2 and are all of a sudden not getting logs in stderr (using in a node script). The regressions seems to have been caused by #799

Admittedly we're perhaps using the library not exactly in a way that it was intended to be used. We aren't setting DEBUG environment variable, so process.env.DEBUG is undefined, but our namespaces are named example-namespace* with a trailing *. These were previously logging, now they're not.

twhitbeck avatar Sep 03 '21 14:09 twhitbeck

example-namespace*

FWIW this isn't really supported, and dare I say deprecated; you should attempt to remove those ASAP.

I'll have to take a look and see, but you're the only one reporting this so I have to assume (without checking) that it's related.

Qix- avatar Sep 12 '21 21:09 Qix-

ok

ulysses2000 avatar Sep 13 '21 17:09 ulysses2000