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
Hi,
First thank you very much for the lib, it did save me a lot of time.
The only issue I have now is that I cannot debug my app when a WorkerFarm is running.
Those are the errors I'm having:
Failed to open socket on port XXX, waiting 1000 ms before retrying
Looks like each child process' debugger is bound to the same debug port thus the error message and the connection loss with the main process.
Looks like it's a bug in node, which was fixed in v0.11 but not backported to v0.10 (which I'm using) nodejs/node-v0.x-archive#5318
The text was updated successfully, but these errors were encountered:
brianreavis
added a commit
to naturalatlas/node-worker-farm
that referenced
this issue
May 22, 2015
Easy way to make it work with debugger;
//some of my lil code
let isDebug = typeof v8debug !== 'undefined';
let worker = isDebug ? require('./Queue/Worker.js') : workerFarm({
maxCallsPerWorker : 1000
, maxConcurrentWorkers : this.threads
, maxConcurrentCallsPerWorker : 1
, maxConcurrentCalls : this.threads
, maxCallTime : Infinity
, maxRetries : 1
, autoStart : true
}, require.resolve('./Queue/Worker.js'), ['init','task']);
//
Of course its become sync like and has no acually new processes, but itsenough for some little debug :)
Hi,
First thank you very much for the lib, it did save me a lot of time.
The only issue I have now is that I cannot debug my app when a WorkerFarm is running.
Those are the errors I'm having:
Looks like each child process' debugger is bound to the same debug port thus the error message and the connection loss with the main process.
Looks like it's a bug in node, which was fixed in v0.11 but not backported to v0.10 (which I'm using) nodejs/node-v0.x-archive#5318
The text was updated successfully, but these errors were encountered: