Uh oh!
There was an error while loading. Please reload this page.
stream: avoid destroying writable source - #32198
Conversation
nodejs-github-bot
commented
Mar 11, 2020
MylesBorins
commented
Mar 11, 2020
can we fast track this? I'd like to see it land in the upcoming 13.11.0 release @ronag looks like this needs a rebase |
0506fd0 to
7b3ecccComparerebased @MylesBorins |
nodejs-github-bot
commented
Mar 11, 2020
There was a problem hiding this comment.
A test that has a Duplex piping back in to itself would be good also
There was a problem hiding this comment.
I suppose this is a nit? Since we might want to fast-track this would you mind if I do so in a follow up PR later?
MylesBorins
commented
Mar 11, 2020
@ronag fwiw you can't approve fastrack on your own PR |
ronag
commented
Mar 11, 2020
Np, I was +1 the rebase part of your comment. I'll remove my +1. |
jasnell
commented
Mar 11, 2020
+1 to fast tracking |
nodejs-github-bot
commented
Mar 11, 2020
MylesBorins
commented
Mar 11, 2020
@ronag FWIW this patch is not going to land cleanly on v13.x. You might want to get started on a backport now if you have time. very much trying to get this out in today's release. |
nodejs-github-bot
commented
Mar 11, 2020
User might still want to be able to use the writable side of src. This is in the case where e.g. the Duplex input is not directly connected to its output. Such a case could happen when the Duplex is reading from a socket and then echos the data back on the same socket. Fixes: nodejs@4d93e10#commitcomment-37751035
ronag
commented
Mar 11, 2020
Fixed conflicts |
7b3eccc to
5daaddbComparenodejs-github-bot
commented
Mar 12, 2020
User might still want to be able to use the writable side of src. This is in the case where e.g. the Duplex input is not directly connected to its output. Such a case could happen when the Duplex is reading from a socket and then echos the data back on the same socket. PR-URL: #32198 Refs: 4d93e10#commitcomment-37751035 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
MylesBorins
commented
Mar 12, 2020
landed in 2bfb340 |
User might still want to be able to use the writable side of src. This is in the case where e.g. the Duplex input is not directly connected to its output. Such a case could happen when the Duplex is reading from a socket and then echos the data back on the same socket. Backport-PR-URL: #32212 PR-URL: #32198 Refs: 4d93e10#commitcomment-37751035 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
User might still want to be able to use the writable side
of src. This is in the case where e.g. the Duplex input
is not directly connected to its output. Such a case could
happen when the Duplex is reading from a socket and then echos
the data back on the same socket.
Fixes: 4d93e10#commitcomment-37751035
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes