IssueTracker

Problem you have encountered:

Running yarn install on a project configured with a virtual NPM Artifact Registry fails and reports a 500 Internal Error when yarn has a clean cache.

yarn install v1.22.19
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
error An unexpected error occurred: "https://europe-west2-npm.pkg.dev/zoa-artifacts/npm-virtual/strip-ansi/-/strip-ansi-7.1.0.tgz: Request failed \"500 Internal Server Error\"".
info If you think this is a bug, please open a bug report with the information provided in "/Users/ricardocosta/code/example-service/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

The issue doesn't happen all the time, but happens >80% of the time. The package that fails is never the same.

Our NPM virtual registry uses either a private registry for our internal packages (those packages never error) or a remote registry pointing and npmjs. This started happening today after working without issue for over 3 weeks.

What you expected to happen:

Running yarn install would fetch all packages without error.

Steps to reproduce:

Run rm -rf node_modules && yarn cache clean, "npm_config_registry=https://registry.npmjs.org npx google-artifactregistry-auth", and finally yarn install

Other information (workarounds you have tried, documentation consulted, etc):

The Artifact Registry API shows 0 errors. Requests are within the quota, showing a peak usage of ~20%.

The issue has been reproduced in several different machines.

Running yarn install --verbose show that only one of the packages fails the download but all others are successful (before and after the failure). A second yarn install successfully downloads the missing package from the previous run and succeeds (the remaining packages are obtained from cache).