10 months ago
our nixpacks build is failing with this error
stage-0
RUN GIT_SSH_COMMAND='ssh -i /root/.ssh/id_rsa -o IdentitiesOnly=yes' yarn install --check-cache
711ms
Internal Error: Server answered with HTTP 500 when performing the request to https://repo.yarnpkg.com/4.12.0/packages/yarnpkg-cli/bin/yarn.js; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
at ClientRequest. (/nix/store/fkyp1bm5gll9adnfcj92snyym524mdrj-nodejs-22.11.0/lib/node_modules/corepack/dist/lib/corepack.cjs:42205:23)
at Object.onceWrapper (node:events:633:26)
at ClientRequest.emit (node:events:518:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:704:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:117:17)
at TLSSocket.socketOnData (node:_http_client:546:22)
at TLSSocket.emit (node:events:518:28)
at addChunk (node:internal/streams/readable:561:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:512:3)
at Readable.push (node:internal/streams/readable:392:5)
Dockerfile:25
-------------------
23 | RUN --mount=type=cache,id=s/0ade5086-3efb-4495-95f3-6080b95b372e-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 GIT_SSH_COMMAND='ssh -i /root/.ssh/id_rsa -o IdentitiesOnly=yes' ssh -T [email protected] || true
24 | RUN --mount=type=cache,id=s/0ade5086-3efb-4495-95f3-6080b95b372e-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 npm install -g [email protected] && corepack enable
25 | >>> RUN --mount=type=cache,id=s/0ade5086-3efb-4495-95f3-6080b95b372e-/usr/local/share/cache/yarn/v6,target=/usr/local/share/.cache/yarn/v6 GIT_SSH_COMMAND='ssh -i /root/.ssh/id_rsa -o IdentitiesOnly=yes' yarn install --check-cache
26 |
27 | # build phase
-------------------
confirmed that yarn is reachable. builds on CI are succeeding.
6 Replies
10 months ago
all good now
10 months ago
would be helpful to understand a root cause and what to do moving forward when this happens - we had an urgent bug fix we couldnt deploy for ~2 hrs
tylerjohnsondagoat
<https://www.githubstatus.com/> showing some errors there. related?
10 months ago
Indeed it is, we're investigating the availability of the external package provider. Once we have final confirmation we can call something.
Status changed to Awaiting User Response Railway • 10 months ago
10 months ago
Okay- it does seem to be isolated to the yarnpkg repo. We don't have a ext. outage source for that one, but we will call one so that others are in the loop there.
10 months ago
Okay, appears to be resolved. Going to mark this one as solved for everyone on this thread.
Status changed to Solved angelo-railway • 10 months ago
