Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: why do we filter messages? #6

Closed
yoshuawuyts opened this issue Jul 14, 2018 · 3 comments
Closed

Question: why do we filter messages? #6

yoshuawuyts opened this issue Jul 14, 2018 · 3 comments

Comments

@yoshuawuyts
Copy link
Contributor

@killercup you're probably the right person to ask, but: why are we filtering messages in .setup_env_logger()?

I can imagine it being useful to sometimes log out trace messages from library code (e.g. embedded databases, etc.) Should we perhaps introduce a method / flag that doesn't filter?

@killercup
Copy link
Collaborator

It is my understanding that this is a good default and that it can be overwritten by setting the RUST_LOG env var to something like RUST_LOG=foo=trace. Haven't looked at this in a while though

@yoshuawuyts
Copy link
Contributor Author

@killercup ahh yeah, that answers it. Thanks!

@killercup
Copy link
Collaborator

Would be awesome to document that too :)

epage added a commit that referenced this issue Oct 6, 2023
…holder

README.md 'Crates Status' icon link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants