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
Right now, I was puzzling over seeing Error: write after end being output and killing my server. Turns out I had a call to reject in an if statement immediately followed by a call to accept. Obviously not correct code, but the issue is that the error wasn't reported in a way I could catch, and somehow ended up killing my server, which was pretty annoying.
So I'm suggesting that accept/reject check something relevant and throw an error output so it can be caught and handled. Thanks!
The text was updated successfully, but these errors were encountered:
Oh one more note about this, that write after end error wasn't happening before I updated to the new version of this module, so something in there must have changed that caused it. An error should definitely be thrown, but in a different way.
Right now, I was puzzling over seeing
Error: write after end
being output and killing my server. Turns out I had a call toreject
in an if statement immediately followed by a call toaccept
. Obviously not correct code, but the issue is that the error wasn't reported in a way I could catch, and somehow ended up killing my server, which was pretty annoying.So I'm suggesting that accept/reject check something relevant and throw an error output so it can be caught and handled. Thanks!
The text was updated successfully, but these errors were encountered: