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
If you try to send to an stored client-socket and the client is currently unavailable you've got an exception.
events.js:72
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at errnoException (net.js:904:11)
at TCP.onread (net.js:558:19)
The problem is: When the socket receive an error over socket.on('error', callback(event) and the event is empty or undefined, that breaks the complete Node.js application.
I've solved the problem but i will test it currently. I will make a pull request today.
The text was updated successfully, but these errors were encountered:
If you try to send to an stored client-socket and the client is currently unavailable you've got an exception.
The problem is: When the socket receive an error over
socket.on('error', callback(event)
and the event is empty orundefined
, that breaks the complete Node.js application.I've solved the problem but i will test it currently. I will make a pull request today.
The text was updated successfully, but these errors were encountered: