-
Notifications
You must be signed in to change notification settings - Fork 763
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: use log level 1 for debug #3039
Conversation
todo Signed-off-by: alex <8968914+acpana@users.noreply.github.com>
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #3039 +/- ##
==========================================
- Coverage 52.49% 52.46% -0.03%
==========================================
Files 134 134
Lines 11937 11948 +11
==========================================
+ Hits 6266 6269 +3
- Misses 5179 5188 +9
+ Partials 492 491 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
☔ View full report in Codecov by Sentry. |
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.
Thanks! LGTM
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.
LGTM
Signed-off-by: alex <8968914+acpana@users.noreply.github.com>
Verbosity log levels (V level) are additive so starting at 2 is actually a higher level than
Debug
. So in effect, today, if users uselog-level=DEBUG
any log line that usesloggging.Debug
as its V level will not see the line since we don't have a control for higher verbosity (>1) yet.Not sure why it was 2 to begin with but I think it may have been missed on the original PR that introduced it #482.