-
Notifications
You must be signed in to change notification settings - Fork 116
Updating Web Platform Tests can cause ERR_STREAM_PREMATURE_CLOSE
#626
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
Comments
|
ERR_STREAM_PREMATURE_CLOSE
ERR_STREAM_PREMATURE_CLOSE
@targos Thanks for the info. Very helpful. Yes, it's true that there is a minimum required version for If it is important that this project is able to run on older versions of Node, we'll need to formulate a different fix for the above issue. Currently, it seems that the WPT Perhaps we could check the version of Node.js and lazily load |
I think it's important that this tool can run on the Node.js versions that are most likely used by our collaborators. I'd be +1 on removing support for Node.js 12. Not sure about 14. |
Every single WPT update i'm fighting this error with a while loop. Took 15 minutes of looping now to update WPTs. |
We can probably drop support for 14 at this point. |
Issue
When updating WPT
resources
, I received aERR_STREAM_PREMATURE_CLOSE
error. I also tested updatingstreams
and I did not see the error. I'm not sure whether this is due to the size of data being downloaded.Node version (tried multiple): v19, v16, v14
Hardware:
Suggested Fix
Switching to
undici
fromnode-fetch
fixed the issue 😬 ! I'll open a PR.The text was updated successfully, but these errors were encountered: