Some https://nodejs.org/dist/ builds are experiencing intermittent 500 errors #32683
Comments
ryanolee
changed the title
|
Facing this issue as well |
|
Seems that it affects all or most builds. If you try downloading the same file multiple times then it's hit or miss, I get approximately 70% |
|
This is not only happening for builds but the entire https://nodejs.org site in general is giving random 500 errors See also: |
|
Only the v12.16.1 version is working at the moment. Seems to be an issue on Node site. I've just used the 12.16.1 version for now but its not going to be a solution for everyone. |
ryanolee
changed the title
|
Facing same issue. Is there any workaround? |
You can try to use Docker images 👍 |
no issue - using the setup-node action is currently failing because of an upstream issue - nodejs/node#32683 - this commit switches to using a Docker container
|
Same issue .. |
|
Same issue. https://nodejs.org/dist/v9.11.1/node-v9.11.1-linux-x64.tar.gz file is missing |
I only managed to have the |
|
We are experiencing the problems for a few hours from now? |
|
Same issue... it is intermittent. |
|
This is blocking our deploy pipeline, how can we help here? It seems rather weird that a project as big as Node has issues reported as far back as 8 hours and there's nothing done about it.. |
|
Is there an update on this issue? This is blocking our build pipelines and we are closing in on a release deadline. |
|
Use apt/yum to install the package for your respective distro. |
|
@nodejs/build-infra |
|
Same Issue. Blocking our release + deployment pipeline totally. Yikes |
|
You, guys, should store copies of all third-party packages in local repository to prevent such failures |
At a big corp i used to work we did that, it saved our asses few times npm has had issues. it's a good idea if you have the resources :) |
|
|
@MaxGsomGsom Some prebuilt systems simply aren’t designed for that. In an ideal world that would be the case. But the practicality of it in many cases is unreasonable or untenable. |
|
I made a ticket for the build team as well nodejs/build#2263 |
|
Hi everyone, Node and Build are aware of issues people are seeing. Unfortunatly the downloads server has access limited to only @nodejs/build-infra which means we have to wait untill one of that team is available to fix the issue. Please keep telling us what you see to help diagnose (though please dont open new issues to avoid clutter) Sorry for any inconvenience caused! |
|
@AshCripps e.g.
|
|
Hi, I'm having this issue : Hope it helps to resolve the problem. |
We see super slow downloads or aborting downloads. From tonight: |
^ This is the relevant issue where you can expect updates. It’s not necessary to comment here with “this is happening for me too” comments – as Ash said, we’re aware of the problem. |
|
This issue happens almost once a month and it's honestly very frustrating. :( |
|
Definitely the first time I remember experiencing this in 3 or 4 years of our builds yanking node down. Right now its working 40% of the time. When it doesn't work, it just 500s at the outset. No partial loading. |
|
Could not download node-linux-x64.tar.gz (org.nodejs:node:10.15.0) |
|
I'll go to the machine to take a look to see if I can see anything obvious as a starting point. |
|
Will use nodejs/build#2263 to comments. |
Sorry for asking... the [single] machine serving all nodejs.org downloads in the world? :D |
Forget where I read it. But I think Cloudflare handles a lot of caching for Node. So it's very possible it is just a single machine, especially with how aggressively Cloudflare can caching stuff. |
I assume he meant his computer. Since @mhdawson has pointed to nodejs/build#2263 as the single source of truth for this discussion, I'm going to lock this discussion in favor of that one. There are already further updates there ❤️ |
|
(Going to leave pinned until resolved so we don't see duplicate issues created.) |
|
@bnb is it possible to leave it open and locked? That might better reflect the situation, if technically possible. |
|
Done ✅ |
|
It's been resolved for some time now, closing. |
and others
See:
nodejs/nodejs.org#3075
nodejs/build#2263
For other node repos effected by this.
What steps will reproduce the bug?
Many /dist/ builds are giving 500 errors. Such as https://nodejs.org/dist/v0.11.15/
How often does it reproduce? Is there a required condition?
Temperamental as it currently stands. Currently 500-ing for me
What is the expected behavior?
Dist zip download
What do you see instead?
500 errors
Additional information
A number of other issues have been raised about this:
#32680
#32681
#32682
We will probably want to flatten them into one global issue surrounding builds across all of these versions failing to properly load.
Currently building a list of effected URLS
Thus far failing builds can be found here <- Likley to change given 500 errors seem almost random at this stage
The text was updated successfully, but these errors were encountered: