You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Consider a root logger that filters on Level.WARNING with a child logger that filters on Level.FINE, but has no listeners.
Once the child logger accepts a message, it propagates up to the root logger and prints, despite being a lower level than the root logger's configuration.
Is the following behavior expected?
Consider a root logger that filters on
Level.WARNING
with a child logger that filters onLevel.FINE
, but has no listeners.Once the child logger accepts a message, it propagates up to the root logger and prints, despite being a lower level than the root logger's configuration.
results in
Of course, adjusting the root logger's handler to be like so can solve this problem:
But this feels redundant.
Is the original behavior expected?
The text was updated successfully, but these errors were encountered: