| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Call the close method after readable 'end' so that 'close' will be emitted afterwards. Fixes: nodejs#32023
There was a problem hiding this comment.
Thank you!
Sorry, something went wrong.
Sorry, something went wrong.
|
@addaleax thanks for such a quick response! |
Sorry, something went wrong.
Sure, done! |
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
<3
Sorry, something went wrong.
|
This had landed on 13.x and was backed out as it seemed to break CI might be best to land as a backport PR |
Sorry, something went wrong.
Call the close method after readable 'end' so that 'close' will be emitted afterwards. Fixes: nodejs#32023 PR-URL: nodejs#32050 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Call the close method after readable 'end' so that 'close' will be emitted afterwards. Fixes: nodejs#32023 PR-URL: nodejs#32050 Reviewed-By: Anna Henningsen <anna@addaleax.net> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
| Back | FazBrowse Home | New Git URL |
Hey there,
as far as I understand this PR breaks behaviour when zlib streams emit close event in case of successful end.
Since emitting close is the part of Readable.destroy implementation - .destroy must be called on ZlibBase instance. In this case (case of successful finish) this.on('end') should be sufficient.
Fixes: #32023
\cc @addaleax