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
It's possible for ServiceBrowser to call update_service after calling remove_service. After adding a bunch of print statements, I think what is happening is:
the remove event is triggered
the remove event is moved from _pending_handlers to the queue
the update event comes in and is added to _pending_handlers (and since the remove event is no longer in _pending_handlers, the check for that lets it pass)
I didn't find a good workaround for this problem, and looking through the code it also looks like an add followed quickly but remove will drop the remove. As a workaround, is there a way to query if the service is still there?
The text was updated successfully, but these errors were encountered:
It's possible for ServiceBrowser to call update_service after calling remove_service. After adding a bunch of print statements, I think what is happening is:
I didn't find a good workaround for this problem, and looking through the code it also looks like an add followed quickly but remove will drop the remove. As a workaround, is there a way to query if the service is still there?
The text was updated successfully, but these errors were encountered: