hexpm / hex

Package manager for the Erlang ecosystem.
https://hex.pm
977 stars 187 forks source link

mix deps.get fails to get packages with Hex 2.0.0 #964

Closed nileshtrivedi closed 2 years ago

nileshtrivedi commented 2 years ago
$ elixir -v
Erlang/OTP 25 [erts-13.1.2] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]

Elixir 1.14.1 (compiled with Erlang/OTP 25)
$ mix hex.info
Hex:    2.0.0
Elixir: 1.14.1
OTP:    25.1.2

Built with: Elixir 1.14.1 and OTP 23.3

Creating new Phoenix application:

mix phx.new hello
cd hello
mix deps.get

Prints the following:

Failed to fetch record for phoenix from registry (using cache instead)
:timeout
Failed to fetch record for phoenix_ecto from registry (using cache instead)
:timeout
:timeout
Failed to fetch record for floki from registry (using cache instead)
** (Mix) No package with name phoenix (from: mix.exs) in registry

The errors are not consistent:

$ mix local.hex
Found existing entry: /Users/eshnil/.asdf/installs/elixir/1.14.1-otp-25/.mix/archives/hex-2.0.0
Are you sure you want to replace it with "https://repo.hex.pm/installs/1.14.0/hex-2.0.0.ez"? [Yn] Y
* creating /Users/eshnil/.asdf/installs/elixir/1.14.1-otp-25/.mix/archives/hex-2.0.0
$ mix deps.get
Failed to fetch record for phoenix from registry (using cache instead)
:timeout
:timeout
Failed to fetch record for phoenix_html from registry (using cache instead)
** (Mix) No package with name phoenix (from: mix.exs) in registry

Here's the deps section in mix.exs file:

     {:phoenix, "~> 1.6.15"},
      {:phoenix_ecto, "~> 4.4"},
      {:ecto_sql, "~> 3.6"},
      {:postgrex, ">= 0.0.0"},
      {:phoenix_html, "~> 3.0"},
      {:phoenix_live_reload, "~> 1.2", only: :dev},
      {:phoenix_live_view, "~> 0.17.5"},
      {:floki, ">= 0.30.0", only: :test},
      {:phoenix_live_dashboard, "~> 0.6"},
      {:esbuild, "~> 0.4", runtime: Mix.env() == :dev},
      {:swoosh, "~> 1.3"},
      {:telemetry_metrics, "~> 0.6"},
      {:telemetry_poller, "~> 1.0"},
      {:gettext, "~> 0.18"},
      {:jason, "~> 1.2"},
      {:plug_cowboy, "~> 2.5"}
nileshtrivedi commented 2 years ago

It worked after some time without any changes in my system or my network. Looks like a temporary CDN issue.