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
Poller.Remove() doesn't actually remove the given socket from the underlying czmq poller, it just removes it from the slice of golang objects wrapping sockets. While I can't explain the exact reason behind it, this is causing weird behavior when sockets are removed from the poller (at the golang level), the sockets are destroyed, and then new sockets are added to the poller. In these cases the poller never notices new reads pending on the new sockets
The text was updated successfully, but these errors were encountered:
Poller.Remove()
doesn't actually remove the given socket from the underlying czmq poller, it just removes it from the slice of golang objects wrapping sockets. While I can't explain the exact reason behind it, this is causing weird behavior when sockets are removed from the poller (at the golang level), the sockets are destroyed, and then new sockets are added to the poller. In these cases the poller never notices new reads pending on the new socketsThe text was updated successfully, but these errors were encountered: