You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under :aliases, the coast deps.edn has a couple of :git/url based dependencies with :sha verification hashes.
One thing that happens is that the shas can change on github when new releases happen there. The ones listed in a new coast project's deps.edn can then fail when importing a new deps project into cursive. The failure shows up as a cryptic 'Auth failure on deps.edn' message.
We've also observed that whether or not you see the failure depends on the previous deps installation history of the machine - so there's probably other state that is relevant to issue which I'm not aware of.
However, updating the deps.edn shas (or commenting those extra-deps out) does get around the issue and allow cursive to create the classpath correctly.
Just leaving this here in case anyone else hits the same problem.
The text was updated successfully, but these errors were encountered:
Under
:aliases
, the coastdeps.edn
has a couple of :git/url based dependencies with:sha
verification hashes.One thing that happens is that the shas can change on github when new releases happen there. The ones listed in a new coast project's
deps.edn
can then fail when importing a new deps project into cursive. The failure shows up as a cryptic 'Auth failure on deps.edn' message.We've also observed that whether or not you see the failure depends on the previous deps installation history of the machine - so there's probably other state that is relevant to issue which I'm not aware of.
However, updating the deps.edn shas (or commenting those extra-deps out) does get around the issue and allow cursive to create the classpath correctly.
Just leaving this here in case anyone else hits the same problem.
The text was updated successfully, but these errors were encountered: