AssertionError: false == true at RoundRobinHandle.add (cluster.js:140:3)

[adrai]

Is this a node issue? Unitech/pm2#1049

[tjfontaine]

Would need to see more information about the test case, but in short that assertion fails when trying to re-add a worker that was already in the pool.

@cjihrig can you take a look at this?

[cjihrig]

@tjfontaine the solution to this is in #8643. It landed in master, but not 0.12.

[adrai]

In which release can I expect to be fixed? v0.12.1 ? v1.0.0 ? Or should I wait for io.js to be merged ;-) ?

[cjihrig]

It appears that I mixed up this issue with #9261 (similar issue titles and stack traces). My original comment applies to #9261, but @adrai can you tell me if your failure involves the use of UDP? If not, can you please provide code with no external dependencies that reproduces the issue.

[adrai]

ok, i tested on an other machine... and I can't reproduce it, so we can close this issue...

[suparngp]

I am still having this issue. I ran the following sample code for express app and it produces the same error

var cluster = require("cluster");
var cpus = require("os").cpus().length - 1;
if (cluster.isMaster) {
    for (var i = 0; i < cpus; i++) {
        cluster.fork();
    }
    return;
}
else {
    var app = require('../app');
    var http = require('http');
    var port = 3000;
    app.set('port', port);
    /**
     * Create HTTP server.
     */
    var server = http.createServer(app);
    /**
     * Listen on provided port, on all network interfaces.
     */
    server.listen(port);
    server.on('error', onError);
    server.on('listening', onListening);
}

assert.js:86
  throw new assert.AssertionError({
        ^
AssertionError: false == true
    at RoundRobinHandle.add (cluster.js:140:3)
    at queryServer (cluster.js:480:12)
    at Worker.onmessage (cluster.js:438:7)
    at ChildProcess. (cluster.js:692:8)
    at ChildProcess.emit (events.js:129:20)
    at handleMessage (child_process.js:324:10)
    at Pipe.channel.onread (child_process.js:352:11)

[solshark]

I have this issue as well

[jvt]

I'm also have this issue.

[blake-jennings]

I am having this issue as well. Are you guys using any workarounds for now?

[austinkelleher]

+1. Anything new on this?