fix: Enable lowering log level below startup value #15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Logger::parse_filters
allows to change the log filter even after the logger has been initialized. However, it was not possible to see logs which were above the level set at startup. E.g. if the logger was initialized withdebug
, setting it totrace
at runtime did not work since the filter of the global logging facade filtered out thetrace
logs.This commit fixes the issue by calling
log::set_max_level
with the level from the updated log filter.