-
Notifications
You must be signed in to change notification settings - Fork 110
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
execute() does not detect socket disconnection #84
Labels
Comments
net.Socket is not sending "end" event on error. It sends "close" in both error and non-error cases, and that's when you need to emit I'll send a PR |
ssinyagin
added a commit
to voxserv/node-esl
that referenced
this issue
Jan 6, 2020
net.Socket emits "end" only on successful closing, but it emits "close" in error conditions as well.
ssinyagin
added a commit
to voxserv/node-esl
that referenced
this issue
Jan 6, 2020
net.Socket emits "end" only on successful closing, but it emits "close" in error conditions as well.
also a branch to fix it in 1.2.1: https://github.com/voxserv/node-esl/tree/v1.2.1-bugfix |
Can you open a PR for that branch to the |
Until this is merged you can set up the callback on your own code.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm running synchronous outbound ESL socket toward the node-esl server. If the server starts an
conn.execute(xxxx)
command, and the socket disconnects during the execution, the execute() never returns and hangs forever.by looking through the sources of Connection.js, I couldn't find any handling for such event.
Here's my code:
The text was updated successfully, but these errors were encountered: