Skip to content
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

Regular errors downloading Node.js tarballs #4254

Closed
shadowspawn opened this issue Sep 28, 2023 · 2 comments
Closed

Regular errors downloading Node.js tarballs #4254

shadowspawn opened this issue Sep 28, 2023 · 2 comments

Comments

@shadowspawn
Copy link
Member

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:

  • 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.xz
curl: (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.xz
23 | 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.xz
curl: (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.

@mcollina
Copy link
Member

You can read more at nodejs/TSC#1416 and nodejs/build#3410.

If you would like to help, there is likely plenty you can do to help fix this problem.

@shadowspawn
Copy link
Member Author

Thanks for the links. I'll close this as a known issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants