Panic when installing any node version

[noahbald]

When I run fnm install --latest (or any other version) I receive the following error

thread 'main' panicked at /Users/brew/Library/Caches/Homebrew/cargo_cache/registry/src/index.crates.io-6f17d22bba15001f/reqwest-0.12.4/src/blocking/client.rs:963:38:
Client::new(): reqwest::Error { kind: Builder, source: Os { code: 2, kind: NotFound, message: "No such file or directory" } }
stack backtrace:
   0: _rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::result::unwrap_failed
   3: reqwest::blocking::client::Client::new
   4: fnm::http::get
   5: fnm::remote_node_index::list
   6: <fnm::commands::install::Install as fnm::commands::command::Command>::apply
   7: fnm::commands::command::Command::call
   8: fnm::cli::SubCommand::call
   9: fnm::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

My version of rustc is 1.78.0

OS: macOS Sonoma 14.5 arm64
Shell: nushell 0.94.2
fnm: 1.37.0 (homebrew)

Is it possible to install a node version manually while this is an issue for me?

[noahbald]

It seems to work in zsh, so at least I can use that for now

[Schniz]

hmmmmmm would be very interesting to know what's the error, maybe it is related to some custom credentials path in your ENV? is there anything interesting happening in your env vars in nushell?

[Schniz]

This method panics if a TLS backend cannot be initialized, or the resolver cannot load the system configuration.

https://docs.rs/reqwest/latest/reqwest/struct.Client.html#method.new

[noahbald]

Don’t think I have any crazy but my laptop does have some vars set up

• several for CA Certs
• http_proxy/https_proxy

[Schniz]

So I assume the best way I can test it is to have malformed CA cert env vars, and then we can use the default instead of panicking, and emit a warning