"304 Not Modified" responses from the registry

[mangeshpatiln]

We are using yarn 1.22.22. Facing following issue due to the buffer-xor-1.0.3.tgz is not available on path.
[2/4] Fetching packages...
error Error: https://registry.yarnpkg.com/buffer-xor/-/buffer-xor-1.0.3.tgz: Request failed "304 Not Modified"
at ResponseError.ExtendableBuiltin (/usr/lib/node_modules/yarn/lib/cli.js:696:66)
at new ResponseError (/usr/lib/node_modules/yarn/lib/cli.js:802:124)
at Request. (/usr/lib/node_modules/yarn/lib/cli.js:66750:16)
at Request.emit (node:events:518:28)
at module.exports.Request.onRequestResponse (/usr/lib/node_modules/yarn/lib/cli.js:142287:10)
at ClientRequest.emit (node:events:518:28)
at HTTPParser.parserOnIncomingClient (node:_http_client:698:27)
at HTTPParser.parserOnHeadersComplete (node:_http_common:119:17)
at TLSSocket.socketOnData (node:_http_client:540:22)
at TLSSocket.emit (node:events:518:28)
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

When we try to access buffer-xor-1.0.2.tgz and buffer-xor-2.0.2.tgz it is available.

[arcanis]

It seems like something broke on the registry. It's strange that every report so far seem to originate from India - could that somehow come from a proxy you'd all be using? I pinged the npm folks on the OpenJS slack, but they're on US timezone, so that may take some time.

[shailendrasingh]

We are trying to install the yarn on a remote server on AWS cloud, it was working fine till yesterday evening. We have started experiencing this issue from today morning onwards.

[arcanis]

Some other reports on Twitter/X; still seems scoped to the india region I think?:

[Yash17Agrawal]

➕

[i-am-gg]

+1 to this, we are facing this issue too

This is from our jenkins server hosted in ap-south-1

[ShellXploit]

+1 @arcanis would you be able to suggest any workarounds we could hit-and-try as we have been facing this issue as well.

[arcanis]

+1 @arcanis would you be able to suggest any workarounds we could hit-and-try as we have been facing this issue as well.

In the future you probably should consider enabling the offline mirror (see this blog post for 1.x, or this page for 2.x/3.x/4.x) to avoid having your builds rely on the npm registry, which is known to be flaky every once in a while. Unfortunately that's something you need to do ahead of time, so it won't help in the present case.

Right now, unless you have a perfect mirror available (I don't have any to recommend, especially since it has security implications), I don't have a workaround to suggest.

[arcanis]

Seems to affect npm as well btw: npm/cli#7986

[sachinjthakur]

Facing same issue since yesterday.

[chiragramimi]

Same issue, 304. not modified.