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
All the examples of non-HTTP/TCP servers seem to all be within self-contained files. I wanted to start these workers from a file however passing in a file path seems to cause cluster to automatically treat it as a HTTP server or similar and tries to call the 'on' and 'listenFD.bind' methods on it. Commenting out the section of code in worker.js seems to allow this to work as I would expect.
Perhaps cluster could check whether 'on' and 'listenFD.bind' methods exist before trying to call them?
All the examples of non-HTTP/TCP servers seem to all be within self-contained files. I wanted to start these workers from a file however passing in a file path seems to cause cluster to automatically treat it as a HTTP server or similar and tries to call the 'on' and 'listenFD.bind' methods on it. Commenting out the section of code in worker.js seems to allow this to work as I would expect.
Perhaps cluster could check whether 'on' and 'listenFD.bind' methods exist before trying to call them?
app.js
server.js
Code in worker.js causing issue
The text was updated successfully, but these errors were encountered: