Closed lukebakken closed 3 years ago
Aha, clearing out various caches has resolved the issue. No idea why:
(23.1.4)lbakken@shostakovich ~/development/Kyorai/cuttlefish (master %=)
$ rm -rf ~/.cache/rebar3/hex/
(23.1.4)lbakken@shostakovich ~/development/Kyorai/cuttlefish (master %=)
$ rm -rf ~/.cache/rebar3/plugins/
(23.1.4)lbakken@shostakovich ~/development/Kyorai/cuttlefish (master %=)
$ rm -rf ~/.cache/rebar3/lib/
(23.1.4)lbakken@shostakovich ~/development/Kyorai/cuttlefish (master %=)
$ rebar3 hex user whoami
===> Fetching rebar3_hex v6.10.2
===> Fetching hex_core v0.7.1
===> Fetching verl v1.0.2
===> Analyzing applications...
===> Compiling hex_core
===> Compiling rebar3_hex
===> Compiling verl
hexpm : rabbitmq (info@rabbitmq.com)
@lukebakken It looks like you were running 6.10.0 in the first instance in which you experienced a crash, but you cleared out a caches and went to 6.10.2 which fixes a backward compat issue with the latest rebar3. I suspect perhaps that was the issue. Are you on the latest rebar3 by chance?
Yes, I upgraded rebar3
first (via rebar3 local upgrade
), before clearing the caches.
👍 I'm glad this is resolved for you then! 😀
I would assume that if a newer version of rebar3_hex
exists that version would be downloaded without me having to clear caches first :man_shrugging:
@lukebakken I believe it's only explicit upgrades. Maybe an option can be added in rebar3 for global plugins to allow for this.
EDIT: For the future and until something changes in rebar3, in order to upgrade global plugins, even after a local upgrade, you must run : rebar3 as global plugins upgrade <name>
where name in this case would be rebar3_hex
.
Erlang 23.1.4 on Arch Linux
Commands run from top of
Kyorai/cuttlefish
repo clone:crash-diagnostic-report.txt