| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Review requested:
|
Sorry, something went wrong.
Fixes: nodejs#40935 Refs: nodejs#40947 Refs: nodejs#42457
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
|
Looking at this now. I agree the hwm === 0 check is incorrect. Not sure about the fix though. Digging into it. |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM!
Sorry, something went wrong.
|
@kanongil Could you rename this PR or create a new one for lazy reading? |
Sorry, something went wrong.
|
Removing author ready as it looks #43648 (comment) needs to be addressed. @ronag please re-add the label if I misinterpreted your comment. |
Sorry, something went wrong.
|
This issue/PR was marked as stalled, it will be automatically closed in 30 days. If it should remain open, please leave a comment explaining why it should remain open. |
Sorry, something went wrong.
|
Closing this because it has stalled. Feel free to reopen if this issue/PR is still relevant, or to ping the collaborator who labelled it stalled if you have any questions. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
This undoes a patch from #40947, and reworks it to continue handling backpressure when highWaterMark: 0, as described in #42457 (comment).
The new test fails on node releases with the patch from #40947, like v16.4, and passes on node v14 and node v16.3 from before it was introduced. It is also designed, so that it will fail if highWaterMark: 1 is set instead.