Remove zeroconf listener removal workaround

0.132.1 fixes the problem with removing a listener from inside a listener
This commit is contained in:
J. Nick Koston 2024-04-12 19:24:37 -05:00
parent 725e501815
commit 50075747cf
No known key found for this signature in database
2 changed files with 2 additions and 7 deletions

View File

@ -413,16 +413,11 @@ class ReconnectLogic(zeroconf.RecordUpdateListener):
self._cli.log_name,
record_update.new,
)
# We can't stop the zeroconf listener here because we are in the middle of
# a zeroconf callback which is iterating the listeners.
#
# So we schedule a stop for the next event loop iteration as well as the
# connect attempt.
#
# If we scheduled the connect attempt immediately, the listener could fire
# again before the connect attempt and we cancel and reschedule the connect
# attempt again.
#
self.loop.call_soon(self._connect_from_zeroconf)
self._connect_from_zeroconf()
self._accept_zeroconf_records = False
return

View File

@ -1,7 +1,7 @@
aiohappyeyeballs>=2.3.0
async-interrupt>=1.1.1
protobuf>=3.19.0
zeroconf>=0.128.4,<1.0
zeroconf>=0.132.1,<1.0
chacha20poly1305-reuseable>=0.12.1
cryptography>=42.0.2
noiseprotocol>=0.3.1,<1.0