Download slow, breaking CI

[johnpangalos]

Hello,

I noticed that the download speed of node js has become rather slow which breaks a our azure pipeline task. Basically it times out and our build doesn't continue.

Any help with this would be appreciated and let me know if you need anything from me, thanks!

Azure task

what i've seen is that nodejs.org itself is erroring out with error 500 for the past 30-40 minutes, now seems to be up again

[johnpangalos]

Download still seems to be slow unfortunately, even if the site is up.

[adamayoung]

Also getting this in my Azure Pipeline when trying to install Node 13.x

[mihaimircea]

Same error for trying to install node 12.16.1, from ubuntu-latest on Azure Pipelines

[johnpangalos]

I think the problem is that when the download takes too long the node azure pipelines task times out/is unable to use a half downloaded file. Trying the work around of just using the node apt package (I also use ubuntu)

[Moussto]

It's being tracked here nodejs/node#32683

[johnpangalos]

Ok, I'll close then.

[johnpangalos]

This is still technically a problem, and the more eyes on it the better.

[ErisDS]

This is causing a lot of problems with CI/build tools and in cases where these are charged for computation time, costing people a lot of money:

actions/setup-node#132

[joepie91]

This is causing a lot of problems with CI/build tools and in cases where these are charged for computation time, costing people a lot of money

This sort of comment is really not okay.

It's not the build team's problem nor responsibility if people haven't bothered to set up some local redundancy/caching and the resulting failures are costing them money, especially for a free service. Everyone's business/infrastructure continuity is their own responsibility.

I'm sure they have enough on their mind already, without additional pressure from "this is costing us money!" type comments.

[fishcharlie]

@joepie91

This sort of comment is really not okay.

It's not the build team's problem nor responsibility if people haven't bothered to set up some local redundancy/caching and the resulting failures are costing them money, especially for a free service. Everyone's business/infrastructure continuity is their own responsibility.

I'm sure they have enough on their mind already, without additional pressure from "this is costing us money!" type comments.

This is fair. I do think it's extremely important to realize the increased frustration due to the size and impact of Node.js. The larger an open source project becomes, the more responsibility it has. I think it's fair to hold a project the size of Node.js to a higher standard than most open source projects.

It's nearly impossible in this day and age to have 0 dependencies and 100% redundancy.

The reality is that it is costing people money. It's also important to understand that yes, in an ideal world, redundancy and caching should exist. But a lot of systems don't have very good support for that. This is not an ideal world.

The Node.js team should take responsibility for this. It's unfair to place all the blame or responsibility on them. I think most of the frustration is due to the lack of updates from the Node.js team. And I believe that frustration is warranted.

For me personally, all I ask is more transparency and updates from the Node.js team.