Fix ServiceBrowser infinite looping when zeroconf is closed before its canceled#1008
Merged
bdraco merged 1 commit intoOct 10, 2021
Merged
Conversation
…s canceled - If the ServiceBrowser was not canceled before Zeroconf was closed out, and it was not started by Zeroconf itself, it could lead to an infinite scheduling loop
Codecov Report
@@ Coverage Diff @@
## master #1008 +/- ##
=======================================
Coverage 99.76% 99.76%
=======================================
Files 23 23
Lines 2504 2504
Branches 409 409
=======================================
Hits 2498 2498
Misses 3 3
Partials 3 3
Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
out, and it was not started by Zeroconf itself, it could lead
to an infinite scheduling loop
Fixes #1005