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
Seems to me that Node's runtime is actually faster than PHP, and for that reason, the node server actually closes the connection when running the server's stop() method. This means that the connection as well as the process are closed:
The socket is being read / closed. Which throws the initial warning
The process is actually killed. Which throws the error with the Process component.
When stopping the server, the
Connectionclass throws the following warning:As well as a
RuntimeExceptionwith the following message: "unable to kill the process".Removing the following line from the abstract
Serverclass actually fixes the issue.Seems to me that Node's runtime is actually faster than PHP, and for that reason, the node server actually closes the connection when running the server's
stop()method. This means that the connection as well as the process are closed: