Skip to content

Fixed false logging warning #273

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

Merged
merged 1 commit into from
Jun 2, 2020

Conversation

gjbadros
Copy link

@gjbadros gjbadros commented Jun 2, 2020

when there is nothing to write, we don't need to warn about not making progress.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.07%) to 92.386% when pulling b37b6a3 on gjbadros:cleanup_loggin_27_0 into beff998 on jstasiak:master.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.08%) to 92.373% when pulling b37b6a3 on gjbadros:cleanup_loggin_27_0 into beff998 on jstasiak:master.

@jstasiak jstasiak merged commit 10065b9 into python-zeroconf:master Jun 2, 2020
jstasiak pushed a commit that referenced this pull request Jun 2, 2020
When there is nothing to write, we don't need to warn about not making progress.
@bdraco
Copy link
Member

bdraco commented Jun 5, 2020

Verified the spurious warning is fixed in 0.27.1

Thanks @gjbadros and @jstasiak

@gjbadros
Copy link
Author

gjbadros commented Jun 5, 2020 via email

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.

4 participants