-
Notifications
You must be signed in to change notification settings - Fork 18
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: Log level could not be configured from settings #581
Conversation
Please note, only experienced developers should review this PR as it involves significant architectural changes and potential for introducing bugs or instability. The label 'BLACK' is used sparingly to indicate these high risk PRs. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #581 +/- ##
=======================================
Coverage 62.66% 62.66%
=======================================
Files 68 68
Lines 6029 6030 +1
Branches 638 638
=======================================
+ Hits 3778 3779 +1
Misses 2101 2101
Partials 150 150 ☔ View full report in Codecov by Sentry. 🚨 Try these New Features:
|
75d9aee
to
87160c4
Compare
87160c4
to
71cf478
Compare
71cf478
to
9afee87
Compare
rebased on main |
9afee87
to
0d2a1ac
Compare
Solution: Add a `LOG_LEVEL` setting defaulting to "WARNING".
0d2a1ac
to
fdbf4b0
Compare
Co-authored-by: Hugo Herter <[email protected]>
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.
Just tested it and it doesn't seems to work
Replaced by #724 which implement the feature |
Solution: Add a
LOG_LEVEL
setting defaulting to "WARNING".