Launch_provider failing with fuels_rs 0.64.0: Received corrupt message

General
1

When running fuels-rs 0.64.0 tests and calling launch_provider_and_get_wallet() and other variations.

Command

launch_provider_and_get_wallet().await?;

Error

Error: io: Error making HTTP request: error sending request for url
(https://127.0.0.1:62649/v1/graphql):
error trying to connect: received corrupt message of type InvalidContentType

Fuelup show

nightly-aarch64-apple-darwin (override), path:
  forc : 0.61.0+nightly.20240623.c186d93155
    - forc-client
      - forc-deploy : 0.61.0+nightly.20240623.c186d93155
      - forc-run : 0.61.0+nightly.20240623.c186d93155
    - forc-crypto : 0.61.0+nightly.20240623.c186d93155
    - forc-debug : 0.61.0+nightly.20240623.c186d93155
    - forc-doc : 0.61.0+nightly.20240623.c186d93155
    - forc-explore : 0.28.1+nightly.20240623.4bb7392eed
    - forc-fmt : 0.61.0+nightly.20240623.c186d93155
    - forc-lsp : 0.61.0+nightly.20240623.c186d93155
    - forc-tx : 0.61.0+nightly.20240623.c186d93155
    - forc-wallet : 0.8.0+nightly.20240623.d8bb6ed3e1
  fuel-core : 0.30.0+nightly.20240623.4d6167dc63
  fuel-core-keygen : not found
2

I wonder why the value of fuel-core-keygen is not found for you. these are the output for fuelup show for me

Default host: aarch64-apple-darwin
fuelup home: /Users/nazeeh/.fuelup

installed toolchains
--------------------
beta-4-aarch64-apple-darwin
beta-5-aarch64-apple-darwin
latest-aarch64-apple-darwin (default)
0.56.0
nightly-2024-04-12-aarch64-apple-darwin
nightly-2024-06-19-aarch64-apple-darwin
testnet-aarch64-apple-darwin

active toolchain
----------------
latest-aarch64-apple-darwin (default)
  forc : 0.60.0
    - forc-client
      - forc-deploy : 0.60.0
      - forc-run : 0.60.0
    - forc-crypto : 0.60.0
    - forc-debug : 0.60.0
    - forc-doc : 0.60.0
    - forc-explore : 0.28.1
    - forc-fmt : 0.60.0
    - forc-lsp : 0.60.0
    - forc-tx : 0.60.0
    - forc-wallet : 0.7.1
  fuel-core : 0.26.0
  fuel-core-keygen : 0.26.0

So, can you try running fuelup self update?
Secondly, it seems that you are having an issue connecting to the node.
Are you running these commands that would start the server that you are trying to connect with?

let server = FuelService::start(
    NodeConfig::default(),
    ChainConfig::default(),
    StateConfig::default(),
)
.await?;
 
// Create a client that will talk to the node created above.
let client = Provider::from(server.bound_address()).await?;
assert!(client.healthy().await?);
3

It seems as though there was an issue of some kind with my dependencies, i suspect cargo dependencies.

After a fuelup self update and a cleaning of cargo dependencies the problem is resolved.

Thanks for the suggestions.