Potential Run-Time Bug in lib/socket.io/listener.js about socket.io HOT 3 CLOSED

Ah, more information, this warning is posted just before the error.
The 'tcp' module is now called 'net'. Otherwise it should have a similar interface.

The error seems occurs while attempting to include lib/socket.io/transports/flashsocket.js

I think this is triggering the warning, and perhaps the error:
tcp = require('tcp'),

from socket.io.

Nope, that's only triggering the warning.

The error comes when trying to listen to the port.

var temp_server = tcp.createServer(function(socket){

....

});
temp_server.listen(843);

There's a problem with the listen function, and I believe it's firing and Access warning, this all leads to this interesting bit of Node.js code for that listen function.

} else if (!arguments[1]) {
// Don't bind(). OS will assign a port with INADDR_ANY.
// The port can be found with server.address()
self.type = 'tcp4';
self.fd = socket(self.type);
bind(self.fd, arguments[0]);
process.nextTick(function () {
self._doListen();
});
}

The comment is saying the "Don't use bind()", but the code is clearly doing just that.

Maybe it's a comment to us - We've moved to a new "net" class, and a new way of doing things.

Digging down the rabbit hole...

from socket.io.

Commented out the listen(843), but that will probably come back to bite me.

Getting somewhere...
http://brandissimo.com/cdemo/tmp_w1il6

from socket.io.