Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't clobber a previously set level filter #117

Merged
merged 1 commit into from Nov 11, 2018
Merged

Don't clobber a previously set level filter #117

merged 1 commit into from Nov 11, 2018

Commits on Nov 11, 2018

  1. don't clobber a previously set level filter 

    There's a bit of a race with the `log` API for initializing because
it covers two atomic values. It's possible to observe a logger and
attempt to use it before the max level is set. This change doesn't
really make that race any racier than it was already, it just prevents
the surprising behaviour of clobbering a previously set max level
filter even if the logger itself isn't set.
    @KodrAus
    KodrAus committed Nov 11, 2018
    Copy the full SHA
    21858cd View commit details
    Browse the repository at this point in the history