stream: don't flush destroyed writable by ronag · Pull Request #29028 · nodejs/node

It doesn't make much sense (and is a bit weird) to flush a stream which has been destroyed.

I need help creating a relevant test for this.

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• tests and/or benchmarks are included
• documentation is changed or added
• commit message follows commit guidelines

NOTE TO SELF: Look into needFinish & stream destroyed. errorOrDestroy added in this PR should preferably be async.

Hmm.. I'm thinking this is more bug fix than breaking change. What do you think @mcollina?

This will need a unit test.

I'm happy to land this as a bug fix as long as it does not break anything on CITGM.

I would still consider this a bugfix, but we should:

1. verify that CITGM passes
2. let it bake for LTS (10.x) for some time before backporting.

@mcollina: Sorry, found further issues.

Consider the updated tests. We now will throw ERR_STREAM_DESTROYED on some tests that assume ERR_STREAM_WRITE_AFTER_END also we now send the err on the write callback and don't emit it as an error on the stream.

How should this be?

Ok, I think everything (expect @mcollina's comment on !err && chinksWritten++) is fixed in a sensical manner.