Skip to content

Commit

Permalink
child_process: flush consuming streams
Browse files Browse the repository at this point in the history
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: #4049
PR-URL: #4071
Reviewed-By: Colin Ihrig <[email protected]>
  • Loading branch information
Dave authored and cjihrig committed Dec 1, 2015
1 parent b3313aa commit 34b535f
Show file tree
Hide file tree
Showing 2 changed files with 18 additions and 1 deletion.
2 changes: 1 addition & 1 deletion lib/internal/child_process.js
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ util.inherits(ChildProcess, EventEmitter);
function flushStdio(subprocess) {
if (subprocess.stdio == null) return;
subprocess.stdio.forEach(function(stream, fd, stdio) {
if (!stream || !stream.readable || stream._consuming)
if (!stream || !stream.readable)
return;
stream.resume();
});
Expand Down
17 changes: 17 additions & 0 deletions test/parallel/test-child-process-flush-stdio.js
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
'use strict';
const cp = require('child_process');
const common = require('../common');
const assert = require('assert');

const p = cp.spawn('echo');

p.on('close', common.mustCall(function(code, signal) {
assert.strictEqual(code, 0);
assert.strictEqual(signal, null);
}));

p.stdout.read();

setTimeout(function() {
p.kill();
}, 100);

0 comments on commit 34b535f

Please sign in to comment.