Shadow-cljs - dependency update failed - Failed to collect dependencies at thheller:shadow-cljs:jar:2.2.26

[kurtharriger]

I started getting this error on our build servers today. Branch build passed yesterday before merge so doesn’t appear to be code related. Perhaps our build engineering team changed something on the build environment, but our builds run in docker containers so I don’t think that changed either.

Any idea’s what might be causing this and/or how to get some more details as to why this fails?

shadow-cljs - config: /synchrony/prosemirror-synchrony-plugin/shadow-cljs.edn version: 2.2.26
Picked up JAVA_TOOL_OPTIONS: -XX:+IgnoreUnrecognizedVMOptions -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap
OpenJDK 64-Bit Server VM warning: Option UseCGroupMemoryLimitForHeap was deprecated in version 10.0 and will likely be removed in a future release.
shadow-cljs - updating dependencies
shadow-cljs - dependency update failed - Failed to collect dependencies at thheller:shadow-cljs:jar:2.2.26
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

[thheller]

Hmm not a clue.

Seems like it fails to download this file:
https://clojars.org/repo/thheller/shadow-cljs/2.2.26/shadow-cljs-2.2.26.pom

Maybe clojars.org or maven in general was blocked recently?

If you have access to deps.edn or lein in your build environments you could check if they work. Given that they do the exact same stuff that shadow-cljs tries to do that is unlikely but they might give better errors.

[kurtharriger]

We discovered the issue originated with a version bump to yarn.

Our build script is installing latest version of yarn using apt-get and thus when yarn 1.7.0 was released yesterday our builds started to fail. Modifying our build script to explicitly use yarn 1.6.0 resolved the build issues.

We believe this is probably related to https://github.com/yarnpkg/yarn/issues/5874