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.

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

Don't clobber a previously set level filter #117

Merged

Conversation

KodrAus
Copy link
Collaborator

@KodrAus KodrAus commented Nov 11, 2018

Closes #116

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.

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 merged commit fa6a7df into rust-cli:master Nov 11, 2018
@KodrAus KodrAus deleted the fix/retain-previously-set-max-level branch November 11, 2018 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant