-
Notifications
You must be signed in to change notification settings - Fork 30.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
stream/promise finished behavior changed when upgrade from 20.13.1 to 20.16.0 #54131
Comments
Thanks for the report, the issue actually comes from I could submit a patch at the meanwhile to fix this but please be mindful the package has been publicly archived. |
Could suggest any alternative package for something like "in memory stream"? |
This is fixed in the |
Thanks~ |
Version
20.16.0
Platform
Subsystem
No response
What steps will reproduce the bug?
I use he archiver from package
"archiver": "^7.0.1"
and try to archive some files to a stream. I use finished function to wait for the stream completed.How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
finished should behave as the Nodejs v20.13.1
What do you see instead?
finished never returns
Additional information
No response
The text was updated successfully, but these errors were encountered: