stdout not usable after pipeline?

[ronag]

#33166 (comment) @jasnell

I don't know if it's relevant to this specific issue, but I did notice that between 13.11 and and 13.12, when any stream piping to process.stdout or process.stderr closes, process.stdout/process.stderr end up closing allowing no further output. This behavior is carried over into 14.x and is on all platforms...

To give it a quick test, nvm use 13.11 and try...

$ node
Welcome to Node.js v13.11.0
Type ".help" for more information.
> const w = new stream.PassThrough()
undefined
> stream.pipeline(w, process.stdout, () => {})
<truncated>
> w.end('hello')
<truncated>

You'll see that on 13.11, process.stdout is still usable while on anything beyond 13.12, it is not.

[ronag]

I was suspecting #32373, but that was included in 13.13...

[ronag]

@jasnell Are you sure this broke on 13.12? I can't reproduce it on 13.12, only 13.13. I think it's the referenced commit above on 13.13.

[ronag]

@vweevers Thoughts?

#32363
#32363 (comment)
#32373

[jasnell]

Ah, yep yep, you're right, 13.13. Must have selected the wrong version earlier switching between them. The regression starts in 13.13

[vweevers]

To avoid going in circles, could you explain why you consider this to be an issue? Because it contradicts decisions made in #23053, which removed the following restrictions on stdout/stderr:

2. They cannot be closed (end() will throw).
3. They will never emit the 'finish' event.

[ronag]

@jasnell

[ronag]

This has become stale. Closing.