Skip to content

not getting any output #837

Closed
Closed

Description

@twhitbeck

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.

Activity

  1. Qix- commented on Sep 12, 2021

    @Qix-
    Member

    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.

  2. added
    bugThis issue identifies a malfunction
    on Sep 12, 2021
  3. ulysses2000 commented on Sep 13, 2021

    @ulysses2000
  4. abbylyra commented on Jul 5, 2024

    @abbylyra

    Hi, the docs debug.js say

    Conventions
    If you append a "*" to the end of your name, it will always be enabled regardless of the setting of the DEBUG environment > variable. You can then use it for normal output as well as debug output.

    If this is deprecated i would remove it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugThis issue identifies a malfunction

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions