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

Node.js 23.2.0 failed fetching #160

Closed
nschonni opened this issue Nov 12, 2024 · 9 comments · Fixed by #161
Closed

Node.js 23.2.0 failed fetching #160

nschonni opened this issue Nov 12, 2024 · 9 comments · Fixed by #161

Comments

@nschonni
Copy link
Member

Hit a 404 on the fetch job https://unofficial-builds.nodejs.org/logs/202411112036-v23.2.0/
Not sure if that's related to some of the r2 bucket changeover or just a different race condition

@targos
Copy link
Member

targos commented Nov 12, 2024

Probably due to the CF worker not supporting paths like https://nodejs.org/download/release/v23.2.0/node-v23.2.0.tar.xz/../SHASUMS256.txt.asc
@flakey5

targos added a commit to targos/unofficial-builds that referenced this issue Nov 12, 2024
@targos
Copy link
Member

targos commented Nov 12, 2024

I opened #161

@nschonni
Copy link
Member Author

Looks like 18.20.5 also failed, but it got past the SHASUM, but choked on the headers for a similar reason + curl -fsSLO --compressed https://nodejs.org/download/release/v18.20.5/node-v18.20.5.tar.xz/../node-v18.20.5-headers.tar.gz curl: (22) The requested URL returned error: 404

@flakey5
Copy link
Member

flakey5 commented Nov 13, 2024

Looks like 18.20.5 also failed,

There was an incident earlier today with v18.20.5 re nodejs/node#55829

@nschonni
Copy link
Member Author

I'm thinking the jobs might just need to be requeued.

@nschonni
Copy link
Member Author

Looks like 23.2.0 is running now :)
@rvagg could you re-queue 18.20.5 too?

@rvagg
Copy link
Member

rvagg commented Nov 15, 2024

@rvagg
Copy link
Member

rvagg commented Nov 15, 2024

queued 18.20.5, I'll let you monitor and report back if there's a problem 🤞

@nschonni
Copy link
Member Author

Thanks! looks like they both finished and the automated PR got created for the Docker images

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

Successfully merging a pull request may close this issue.

4 participants