-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix the --loglevel flag #114
Conversation
A quick note on the logging module and the log levels: Major changes:
|
Tested, and I think that this PR will need to also include a re-assigning of log levels to messages. There are some messages that aren't assigned proper priority. For example, here is the loglevel set to CRITICAL:
|
After the most recent updates, below is what we see when using CRITICAL log threshold. One note. The
|
Most of the output currently is from files without loggers, which I identified in #130 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks good, other than the one question.
…eption being thrown
Currently, the --loglevel flag does not affect verbosity on the command line/stdout. I would like to change that so that it does affect verbosity on the command line.