| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Edit: Not LGTM yet. Can you please adjust the commit message? We need to account for this behavior here: mainly we need to check that ending might be true while the other state variables (ended, finished) are false. |
Sorry, something went wrong.
|
@mcollina I made some changes in the test, but It was not possible for me to test the fallowing behavior.
The way that functionality is implemented right now is hard to test because they change to true at the "same time" endWritable. This is my first time reading the stream codebase and maybe I'm not seeing something. |
Sorry, something went wrong.
|
@italoacasas you will need to listen to the 'finish' event, which will be emitted in https://github.com/nodejs/node/blob/master/lib/_stream_writable.js#L488 if there are no writes in flight (for which the callback has not be called yet). |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
Sorry, something went wrong.
|
Failures unrelated. This is good to go, I'm planning on merging tomorrow or Friday, if no one else has objections. |
Sorry, something went wrong.
|
Could you capitalize and punctuate the comments in this PR. You also have some typos: 'endeding' should be 'ending' in a few places I think. Other than that LGTM. |
Sorry, something went wrong.
|
Merged in fd16eed. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
Description of change
Issue related: #8686