Closed tompave closed 2 years ago
I had the same issue yesterday. But only on Unix not on Windows.
I've tried again 12-13 hours later, with a brand new project, and now it works.
This suggests it was either a caching issue in the mix/hex client, or the Hex.pm server didn't allow downloading the latest version even though it was displayed in the UI (which could also be a different caching issue on the server).
If it was on the client, I guess a command like mix hex.clear_cache
would be handy.
This should be fixed after a manual CDN purge. We are working on a more permanent solution to this issue but while we do it may happen again. If it does please let us know.
I've encountered what looks like a bug, or possibly some caching issue.
What I've done:
I've installed the Phoenix generator for the first time (it's an almost new machine):
mix phx.new foobar
)cd foobar && mix deps.get
. I've had to explicitly enter the dir and run this myself, because when I answeredY
to the usual prompt after project creation, it failed immediately. It didn't print any details, but I suspect it was the same issue.š„ I would expect the packages to be fetched as usual, but instead I get this error:
1.6.7
has just been published (published today, still zero downloads for this version).mix deps.get --no-archives-check
(a shot in the dark). It didn't work.rm ~/.hex/cache.ets
and then retried. It didn't work.foobar/mix.exs
to downgrade the version of the dependency to{:phoenix, "~> 1.6.6"},
. With that, I can runmix deps.get
successfully.mix deps.get
to fetch the latest version of Phoenix from Hex.pm.