-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
use level config in log section when sub log section not set level #15176
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
Conversation
in previouse if a log subsetcion not set level
it will use ``info`` as default value.
this pr will make default value (``[log] -> LEVEL``) useable.
example config:
```INI
[log]
MODE = console
LEVEL = Trace
[log.console]
LEVEL =
STDERR = false
```
previous result:
```JSON
// console:
{
"level": "info",
...................
}
```
after change:
```JSON
// console:
{
"level": "track",
...................
}
```
Signed-off-by: a1012112796 <[email protected]>
|
not confirm whether it's a bug fix or enhancement .... |
Codecov Report
@@ Coverage Diff @@
## master #15176 +/- ##
=========================================
Coverage ? 43.54%
=========================================
Files ? 668
Lines ? 80600
Branches ? 0
=========================================
Hits ? 35098
Misses ? 39794
Partials ? 5708
Continue to review full report at Codecov.
|
zeripath
left a comment
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.
it's probably a breaking change but definitely looks like an oversight on my behalf
|
LGTM as well. |
in previouse if a log subsetcion not set level
it will use
infoas default value.this pr will make default value (
[log] -> LEVEL) useable.example config:
Prior to this change sub loggers would use the default logger level of
INFOif not set - they will now inherit from the main logger.Administrators should check their log configuration.
Screenshots
previous result:

after:

fix #15170