-
Notifications
You must be signed in to change notification settings - Fork 29.6k
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
net: Create socket and immediately destroy throws AssertionError
#2250
Labels
Comments
Ah found it. PR coming shortly |
Maybe consider adding a test as well, so there's no regression? |
Yep, added one. Thanks for the report |
Heh, looks like there are two PRs out now :) |
Whoops |
My bad. Didn't take into account a user manually destroying the connection before the connection had completed. |
evanlucas
added a commit
to evanlucas/node
that referenced
this issue
Jul 27, 2015
Fixes regression introduced in af249fa. With connect being deferred to the next tick, Socket.destroy could be called before connect. Socket.destroy sets _connecting to false which would cause an assertion error. Fixes: nodejs#2250 PR-URL: nodejs#2251 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Jeremiah Senkpiel <[email protected]> Reviewed-By: Sakthipriyan Vairamani <[email protected]>
Fixed in 503b089. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Starting in v2.3.2, this code which used to work, started to throw an
AssertionError
:With the following exception:
I traced the issue back to this PR by @evanlucas, reviewed by @trevnorris and @cjihrig: #2054
The text was updated successfully, but these errors were encountered: