[v8.x fix] - stream: fix end not being called when reading some base64 files#21089
[v8.x fix] - stream: fix end not being called when reading some base64 files#21089marcosc90 wants to merge 1 commit intonodejs:v8.xfrom marcosc90:fix-19862
Conversation
This fixes 'end' not being called when reading base64 files with highWaterMark equal to: file length - 1, and fixes 'data' not being called on some edge cases when highWaterMark was lower than file length. Fixes: #19862
mscdex
left a comment
There was a problem hiding this comment.
I think we should instead look at backporting whichever commit(s) fixed this particular issue in master rather than pushing some new changes to one particular branch.
|
@nodejs/streams – I can’t tell whether this might be breaking or not |
|
I think this is breaking. Unfortunately the full fix in #17979, which is semver-major for good reasons. We might want to backport that if we need to fix is needed. |
|
Backporting those commits it's not something I would be comfortable with, since I'm not very familiar with the codebase yet. But I would be willing to add some better tests to |
|
@marcosc90 go for it. We definitely need better testing on streams. |
|
I'm closing this based on the above comments |
This fixes
'end'not being called when reading base64 fileswith
highWaterMarkequal to:file length - 1,and fixes
'data'not being called on some edge caseswhen
highWaterMarkwas lower than file length.Fixes: #19862
This issue is still present in
v6.x&v9.xso if everything is ok, I'll submit changes for those versions too.Going through
masterhistory, the same line of code was changed in this commitChecklist
make -j4 test(UNIX), orvcbuild test(Windows) passes