| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Review requested:
|
Sorry, something went wrong.
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #63230 +/- ##
==========================================
- Coverage 90.04% 90.03% -0.01%
==========================================
Files 713 714 +1
Lines 224950 225243 +293
Branches 42530 42572 +42
==========================================
+ Hits 202548 202802 +254
- Misses 14188 14221 +33
- Partials 8214 8220 +6
... and 44 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
Signed-off-by: James M Snell <jasnell@gmail.com>
Sorry, something went wrong.
There was a problem hiding this comment.
This approach looks much better, very nice 👍
I take it this means we're going towards option 1 from my previous backpressure comment? I.e. stream/iter writables are required to always accept one pending write, even in strict mode, and to deal with any internal byte-based limits & backpressure via internal buffering only. Doesn't need to happen immediately, but once we're settled there it'd be good to write that into the stream/iter writer docs explicitly.
Sorry, something went wrong.
There was a problem hiding this comment.
lgtm
Sorry, something went wrong.
|
@pimterry ... I think the backpressure strategy for both stream/iter and this as an application of that api still needs a thorough review, which I plan to get to soon. |
Sorry, something went wrong.
Signed-off-by: James M Snell <jasnell@gmail.com> PR-URL: nodejs#63230 Fixes: nodejs#63216 Reviewed-By: Tim Perry <pimterry@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Signed-off-by: James M Snell <jasnell@gmail.com> PR-URL: nodejs#63230 Fixes: nodejs#63216 Reviewed-By: Tim Perry <pimterry@gmail.com> Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
| Back | FazBrowse Home | New Git URL |
Fixes: #63216