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
DM-33809: Change how --log-level works #658
Conversation
It will be changed later by the log-level call.
Codecov Report
@@ Coverage Diff @@
## main #658 +/- ##
=======================================
Coverage 83.68% 83.69%
=======================================
Files 239 239
Lines 30401 30447 +46
Branches 5098 5106 +8
=======================================
+ Hits 25441 25482 +41
- Misses 3806 3811 +5
Partials 1154 1154
Continue to review full report at Codecov.
|
Encountered during log testing, if the subset is a simple string the command would not print it. Now fallback to using print() if the subset is not a Config.
Now only applies to the lsst logger or logger specified in the environment variable. This will stop non-LSST loggers from contaminating the output.
The lsst logger is always relevant to daf_butler so always set it. DAF_BUTLER_ROOT_LOGGER is now a colon-separated list of additional root loggers.
@@ -0,0 +1,4 @@ | |||
The command-line tooling has changed how it sets the default logger when using ``--log-level``. | |||
Now only the default logger(s) (``lsst`` and the colon-separated values stored in the ``$DAF_BUTLER_ROOT_LOGGER``) will be affected by using ``--log-level`` without a specific logger name. |
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.
See below for possible changes here and in line 4.
Co-authored-by: Kian-Tat Lim <ktl@slac.stanford.edu>
No other logger should have this name.
Now by default only applies to the lsst root logger.
Checklist
doc/changes