Tree: e8e4e0718b

History

Dave 7793c364fc child_process: flush consuming streams When a client calls read() with a nonzero argument on a Socket, that Socket sets this._consuming to true. It never sets this._consuming back to false. ChildProcess.flushStdio() currently doesn't flush any streams where _consuming is truthy. But, that means that it never flushes any stream that has ever been read from. This prevents a child process from ever closing if one of its streams has been read from, causing issue #4049. This commit allows consuming streams to be flushed, and the child process to emit a close event. Fixes: https://github.com/nodejs/node/issues/4049 PR-URL: https://github.com/nodejs/node/pull/4071 Reviewed-By: Colin Ihrig <cjihrig@gmail.com>		9 years ago
..
streams	streams: refactor LazyTransform to internal/	9 years ago
child_process.js	child_process: flush consuming streams	9 years ago
cluster.js	cluster: remove handles when disconnecting worker	9 years ago
freelist.js	iojs: introduce internal modules	10 years ago
linkedlist.js	lib,test: deprecate _linklist	9 years ago
module.js	module,repl: remove repl require() hack	9 years ago
readme.md	doc: add internal modules notice	9 years ago
repl.js	repl: don't crash if cannot open history file	9 years ago
socket_list.js	lib,src: remove usage of events.EventEmitter	9 years ago
util.js	util: move .decorateErrorStack to internal/util	9 years ago

readme.md

Internal Modules

The modules in lib/internal are intended for internal use in Node.js core only, and are not accessible with require() from user modules. These are subject to change at any time. Reliance on these modules outside of core is not supported in any way.