Yarn connectivity issue?

We’re experiencing a lot of build failures lately during the dependencies phase. This happens on CI but does not happen locally. The following logs are the build failures from 6 consecutive builds during the past hour.

error An unexpected error occurred: "https://registry.yarnpkg.com/for-in/-/for-in-0.1.6.tgz: Request failed \"502 Bad Gateway\"".
curl: (22) The requested URL returned error: 500 Internal Server Error
> Failed to download https://yarnpkg.com/latest.tar.gz.
error An unexpected error occurred: "https://registry.yarnpkg.com/minimist/-/minimist-1.2.0.tgz: Request failed \"500 Internal Server Error\"".
error An unexpected error occurred: "https://registry.yarnpkg.com/fuzzaldrin/-/fuzzaldrin-2.1.0.tgz: Request failed \"500 Internal Server Error\"".
error An unexpected error occurred: "https://registry.yarnpkg.com/cjson/-/cjson-0.3.3.tgz: Request failed \"502 Bad Gateway\"".
error An unexpected error occurred: "https://registry.yarnpkg.com/browserify/-/browserify-4.2.3.tgz: Request failed \"500 Internal Server Error\"".
error An unexpected error occurred: "https://registry.yarnpkg.com/markdown-it/-/markdown-it-6.1.1.tgz: Request failed \"500 Internal Server Error\"".

There are no complaints about Yarn on Twitter, so I suspect if there’s connectivity problem between CircleCI and Yarn registry. Does it happen with other Yarn+CircleCI users?

Hello @dtinth,

Are you still experiencing these issues?

Hello. It’s much better now, thanks. :wink:

I still get occasional errors. For example, this happened yesterday:

error Received malformed response from registry for undefined. The registry may be down.

But most builds succeed now.

Thank you!

This is still happening occasionally.

Hackfixed by replacing the command with yarn || yarn.

1 Like

I think they maybe experiencing some growing pains, we can’t do much on our end.

If they have reported any issues in the past, I would suggest to follow their status there.