…nding data every time http://groups.google.com/group/nodejs/browse_thread/thread/16abfa87c32408f3 We have our node.js server monitored by monit, however it seems monit is pretty agressive / quick about closing its connection and thus we've gotten into a loop of errors like this: at #<a ServerResponse>.flush at #<a ServerResponse>.sendBody at [object Object].json at [object Object].[anonymous] at [object Object].[anonymous] at [object Object].[anonymous] http.js:353: Socket is not open for writing connection.send(out, out.encoding); ^ Below is a patch that basically cause flushMessageQueue to check the connection state for each item in the queue rather than just a single time in the beginning.
This function was removed in 368ea93.
In the case of stdin options.fd is 0, which is considered false, therefore fd gets set to null intead of 0. http://groups.google.com/group/nodejs/msg/80849f6aa0b0eaa0
More semantic, since the event will be emitted on connection error, when the connection was ever established.
This was breaking the build on Macintosh.
Similar to the error fixed in 9d3ed1b. Reported by Felix Geisendörfer.
This is same error that was fixed in 216fb3b. Reported by Felix Geisendörfer.