You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users of n are reporting problems with around 5% of Node.js installs in CI failing while downloading the tarball with curl. Three different users, at least two using AWS CodeBuild.
Not got a lot of information, but I thought it was worth asking:
Have there been any recent changes or problems with CDN that might explain increased errors?
Is there anything I can do to make the downloads more reliable? (Specify the http version to use?)
The reported errors are:
fetch : https://nodejs.org/dist/v14.21.3/node-v14.21.3-linux-x64.tar.xzcurl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)fetch : https://nodejs.org/dist/v18.14.2/node-v18.14.2-linux-x64.tar.xz23 | curl: (18) transfer closed with 9476756 bytes remaining to read fetch : https://nodejs.org/dist/v12.16.2/node-v12.16.2-linux-x64.tar.xzcurl: (92) HTTP/2 stream 1 was not closed cleanly: INTERNAL_ERROR (err 2)
Node.js version
Not applicable.
Example code
No response
Operating system
linux-x64 (based on logs supplied)
Scope
All reports describe downloads for Node.js installation running in CI content.
Module and version
Not applicable.
The text was updated successfully, but these errors were encountered:
Details
Users of
n
are reporting problems with around 5% of Node.js installs in CI failing while downloading the tarball with curl. Three different users, at least two using AWS CodeBuild.Not got a lot of information, but I thought it was worth asking:
The reported errors are:
Node.js version
Not applicable.
Example code
No response
Operating system
linux-x64 (based on logs supplied)
Scope
All reports describe downloads for Node.js installation running in CI content.
Module and version
Not applicable.
The text was updated successfully, but these errors were encountered: