The server 'close' event was emitted before the last client 'close' event. Not exactly fatal but potentially confusing. Before this commit the order looked something like [client, server, client], now it looks like [client, client, server]. See #3340 for more details.
* Upgrade V8 to 3.11.1 * Upgrade npm to 1.1.23 * uv: rework reference counting scheme (Ben Noordhuis) * uv: add interface for joining external event loops (Bert Belder) * repl, readline: Handle Ctrl+Z and SIGCONT better (Nathan Rajlich) * fs: 64bit offsets for fs calls (Igor Zinkovsky) * fs: add sync open flags 'rs' and 'rs+' (Kevin Bowman) * windows: enable creating directory junctions with fs.symlink (Igor Zinkovsky, Bert Belder) * windows: fix fs.lstat to properly detect symlinks. (Igor Zinkovsky) * Fix #3270 Escape url.parse delims (isaacs) * http: make http.get() accept a URL (Adam Malcontenti-Wilson) * Cleanup vm module memory leakage (Marcel Laverdet) * Optimize writing strings with Socket.write (Bert Belder) * add support for CESU-8 and UTF-16LE encodings (koichik) * path: add path.sep to get the path separator. (Yi, EungJun) * net, http: add backlog parameter to .listen() (Erik Dubbelboer) * debugger: support mirroring Date objects (Fedor Indutny) * addon: add AtExit() function (Ben Noordhuis) * net: signal localAddress bind failure in connect (Brian Schroeder) * util: handle non-string return value in .inspect() (Alex Kocharin)
In case a fd option is given to fs.createReadStream a read will instantly happen. But in the edge case where fd point to an empty file and .pause() was executed instantly, the end event would emit since no async wait was between fs.createReadStream and the file read there emits end.
Otherwise the cursor position was being reset to 0, even when there was already part of a line, which was strange. Part of #3295.
In case a worker would spawn a new subprocess with process.env, NODE_UNIQUE_ID would have been a part of the env. Making the new subprocess believe it is a worker, this would result in some confusion if the subprocess where to listen to a port, since the server handle request would then be relayed to the worker. This patch removes the NODE_UNIQUE_ID flag from process.env on startup so any subprocess spawned by a worker is a normal process with no cluster stuff.
Fix for joyent/node#3280