-
-
Notifications
You must be signed in to change notification settings - Fork 422
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
Changed the way specific_log_level
flag works in the Logging Configuration
#1769
Changed the way specific_log_level
flag works in the Logging Configuration
#1769
Conversation
Before a pull request is accepted, it must meet the following criteria:
|
Codecov Report
@@ Coverage Diff @@
## master #1769 +/- ##
==========================================
+ Coverage 58.42% 58.45% +0.03%
==========================================
Files 66 66
Lines 6684 6687 +3
==========================================
+ Hits 3905 3909 +4
+ Misses 2779 2778 -1
Continue to review full report at Codecov.
|
28f377d
to
79291e7
Compare
specific
flag works in the Logging Configurationspecific_log_level
flag works in the Logging Configuration
5e3d952
to
7dc8ed6
Compare
Can you write up the bug that this fixes into an issue so we know what is being fixed? |
7dc8ed6
to
21ad1a0
Compare
21ad1a0
to
24c128e
Compare
…uration (tardis-sn#1769) * Changed the logical implementation for the `specific` flag in the debug schema for logging * Fixed the implementation with intended logic * Added logic change for specific_log_level flag * Changed check for specific_log_level parameter & setting it up via the YAML
The current implementation didn't cater to a bug that I have encountered recently. This PR aims to implement the functionality such that we are able to set the
specific
flag default value in thedebug
sub section of thetardis_config.yml
.Description
Motivation and context
How has this been tested?
Type of change
Checklist