-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
socket disconnection flushes itself? #1308
Comments
Apparently, yes. The code for "socket disconnected" frees memory that got initialized during
Don't know. It's built this way, though it doesn't look symmetrical wrt API design. Maybe worth a request to support this use case with the upcoming net module reimplementation in #1080. |
I see, |
If you look at the code |
Hello!
Am trying to write code which reliably connects to a remote TCP socket and keeps trying to reconnect on failures:
I expected to see repeating
TRY
DIS
but saw onlyTRY
DIS
TRY
. So seems that the call tofd:connect
chokes afterfd:on("disconnection", fn)
fired.Wonder do we invalidate somehow
fd
in disconnection handler and is it intended?TIA
The text was updated successfully, but these errors were encountered: