Node 18.19 takes forever to download

2024-07-30T14:37:34.563178035Z Cloning repository...
2024-07-30T14:37:37.208010601Z From https://github.com/minhperry/minhperry.github.io
2024-07-30T14:37:37.20825092Z * branch 775d7b9c22d1f0503f930b502b384de126da7d4d -> FETCH_HEAD
2024-07-30T14:37:37.208269238Z
2024-07-30T14:37:37.295641191Z HEAD is now at 775d7b9 fix: previous commit nullability
2024-07-30T14:37:37.295826628Z
2024-07-30T14:37:37.438490028Z
2024-07-30T14:37:37.438986361Z Using v2 root directory strategy
2024-07-30T14:37:37.475052268Z Success: Finished cloning repository files
2024-07-30T14:37:39.803647211Z Checking for configuration in a wrangler.toml configuration file (BETA)
2024-07-30T14:37:39.804142202Z
2024-07-30T14:37:39.939403639Z No wrangler.toml file found. Continuing.
2024-07-30T14:37:49.012963929Z Detected the following tools from environment: [email protected], [email protected]
2024-07-30T14:37:49.013635631Z Installing nodejs 18.19.1
2024-07-30T14:37:49.648806904Z Trying to update node-build... ok
2024-07-30T14:37:49.783180928Z To follow progress, use 'tail -f /tmp/node-build.20240730143749.560.log' or pass --verbose
2024-07-30T14:37:49.892469133Z Downloading node-v18.19.1-linux-x64.tar.gz...
2024-07-30T14:39:20.267981862Z -> https://nodejs.org/dist/v18.19.1/node-v18.19.1-linux-x64.tar.gz
2024-07-30T14:37:34.563178035Z Cloning repository...
2024-07-30T14:37:37.208010601Z From https://github.com/minhperry/minhperry.github.io
2024-07-30T14:37:37.20825092Z * branch 775d7b9c22d1f0503f930b502b384de126da7d4d -> FETCH_HEAD
2024-07-30T14:37:37.208269238Z
2024-07-30T14:37:37.295641191Z HEAD is now at 775d7b9 fix: previous commit nullability
2024-07-30T14:37:37.295826628Z
2024-07-30T14:37:37.438490028Z
2024-07-30T14:37:37.438986361Z Using v2 root directory strategy
2024-07-30T14:37:37.475052268Z Success: Finished cloning repository files
2024-07-30T14:37:39.803647211Z Checking for configuration in a wrangler.toml configuration file (BETA)
2024-07-30T14:37:39.804142202Z
2024-07-30T14:37:39.939403639Z No wrangler.toml file found. Continuing.
2024-07-30T14:37:49.012963929Z Detected the following tools from environment: [email protected], [email protected]
2024-07-30T14:37:49.013635631Z Installing nodejs 18.19.1
2024-07-30T14:37:49.648806904Z Trying to update node-build... ok
2024-07-30T14:37:49.783180928Z To follow progress, use 'tail -f /tmp/node-build.20240730143749.560.log' or pass --verbose
2024-07-30T14:37:49.892469133Z Downloading node-v18.19.1-linux-x64.tar.gz...
2024-07-30T14:39:20.267981862Z -> https://nodejs.org/dist/v18.19.1/node-v18.19.1-linux-x64.tar.gz
It takes forever to try and download node 18.19, in my 2 most recent pushes. The last 3rd push was about 20min ago and it downloaded fine and it only took 52s. Also, I noticed that since I set NODE_VERSION to 18.19 it will always try to download it every build. Is there anyway to cache it on server instead?
No description
13 Replies
Chaika
Chaika4mo ago
no way to cache it. If you don't need an exact minor version though, if you just specify the major and are using the new build image (default) all of the recent node major version releases are embedded into the build image so you can skip downloading entirely
h
hOP4mo ago
16:53:29.809 Node.js version v18.17.1 detected.
16:53:29.809 The Angular CLI requires a minimum Node.js version of v18.19.
16:53:29.809 Node.js version v18.17.1 detected.
16:53:29.809 The Angular CLI requires a minimum Node.js version of v18.19.
Sadly And apparently it just fails to download 18.19 completely and never halts
Chaika
Chaika4mo ago
sadly nodejs's download cdn can be a fair bit spotty, I don't think they ever fixed that oh the build image defaults to 18.17? rip
h
hOP4mo ago
i could take the risk of downgrading my project to 18.17 and possibly break everything
Chaika
Chaika4mo ago
probably not worth it. Retrying should succeed, or could upgrade to a newer node major (at risk of breaking stuff too)
Walshy
Walshy4mo ago
it's still in the works they have the new path deployed for nightly but not full releases yet afaik
cb
cb4mo ago
Same issue here with Node version. Will this be fixed then? Or at least have a retry. 11:35:21.770 Detected the following tools from environment: [email protected], [email protected] 11:35:21.771 Installing nodejs 18.20.4 11:35:22.375 Trying to update node-build... ok 11:35:22.495 To follow progress, use 'tail -f /tmp/node-build.20240730153522.560.log' or pass --verbose 11:35:22.605 Downloading node-v18.20.4-linux-x64.tar.gz... 11:35:24.884 -> https://nodejs.org/dist/v18.20.4/node-v18.20.4-linux-x64.tar.gz 11:38:37.951 error: failed to download node-v18.20.4-linux-x64.tar.gz 11:38:37.951 -> https://nodejs.org/dist/v18.20.4/node-v18.20.4-linux-x64.tar.gz 11:43:19.918 error: failed to download node-v18.20.4-linux-x64.tar.gz 11:43:19.919 11:43:19.951 BUILD FAILED (Ubuntu 22.04 using node-build 4.9.122-780-g070006d7) 11:43:19.951
Walshy
Walshy4mo ago
it isn't on our end so there is no fix for us this is the best advice i can say
Chaika
Chaika4mo ago
that looks like that did retry, failed multiple times with different timestamps, no?
cb
cb4mo ago
Duh. Yeah I didn't read the full log.
h
hOP4mo ago
https://nodejs.org/en/about/previous-releases Actually is it worth updating to 20/22 now?
Node.js — Node.js Releases
Node.js® is a JavaScript runtime built on Chrome's V8 JavaScript engine.
No description
h
hOP4mo ago
And are any of these version in the build img?
Walshy
Walshy4mo ago
20 and 22 are both in there by default But you can use literally any you want
Want results from more Discord servers?
Add your server