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
{{ message }}
This repository has been archived by the owner on May 3, 2022. It is now read-only.
In v1.x code, .listen() can be called twice in a destructive way. I don't completely understand the path, but the evidence was clear. When using nodejs/cluster, 2 calls to .listen() can occur, and can create 2 different sockets, both listening on the same port. (Observed via lsof.)
In v1.x code, .listen() can be called twice in a destructive way. I don't completely understand the path, but the evidence was clear. When using nodejs/cluster, 2 calls to .listen() can occur, and can create 2 different sockets, both listening on the same port. (Observed via lsof.)
This is avoided in v2 by asserting that .listen isn't already called, and I would propose adding a similar trivial patch to the v1.x branch.
The text was updated successfully, but these errors were encountered: