I was trying to fix this problem described in this topic^ but Faced into another issue
I used fuelup show command to check all components version and after recent sway update cos I keep getting error when run test with following message
and for fuel-core component it returns me this value
forc : 0.38.0+nightly.20230517.29b1d0c47b
- forc-deploy : 0.38.0+nightly.20230517.29b1d0c47b
- forc-run : 0.38.0+nightly.20230517.29b1d0c47b
- forc-doc : 0.38.0+nightly.20230517.29b1d0c47b
- forc-explore : 0.28.1+nightly.20230517.4bb7392eed
What I did is:
>>> which cargo
>>> which fuelup
>>> rm -rf ~/.cargo
>>> rm -rf ~/.fuelup
>>> curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
>>> rustup install stable
>>> rustup update
>>> rustup default stable
>>> curl --proto '=https' --tlsv1.2 -sSf \
https://install.fuel.network/fuelup-init.sh | sh
Error getting version string was still present
>>> fuelup show 12:45:26
Default host: aarch64-apple-darwin
fuelup home: /Users/lidia/.fuelup
forc : 0.40.1
- forc-deploy : 0.40.1
- forc-run : 0.40.1
- forc-doc : 0.40.1
- forc-explore : 0.28.1
- forc-fmt : 0.40.1
- forc-index : 0.16.2
- forc-lsp : 0.40.1
- forc-tx : 0.40.1
- forc-wallet : 0.2.2
fuel-core : Error getting version string
fuel-indexer : Error getting version string
forc : 0.42
And all my test that previously was working started to fail with this error
thread 'local_tests::cancel_order_test::cancel_order_test' panicked at 'error: Could not connect to fuel core server.', /Users/lidia/.cargo/git/checkouts/fuels-rs-ce5f345b87bf4c50/70e531f/packages/fuels-test-helpers/src/node.rs:293:9
I think we talked briefly about this in person!
Let me know if its still an issue so I can escalate it!
Lets try to understand if you got the fuel-core binary in your PATH or not first.
Can you run
If that doesn’t work can you try
Also let’s try to list contents of
Finally, output of
which fuel-core would be perfect to have.
If your problem is not installation/tooling related I will try to find someone from SDK or fuel-core teams so that we can work out your problem together.
Here is my output for all of commands
I think I had the same
My solution was to build fuel-core from source.
However its weird since you are on arm (my issue was on intel)
It might be possible that you have a time machine backup from an
x86_64 mac on an
I don’t think so, is there any way to check it?
Basically the issue is a mess between build
First check if you have multiple builds for the
darwin architecture. For me, when I updated
rustup I would have two builds.
You could try that, let me know if it works for you.
This message comes from different problems. Some people solved it by custom building the bin, others just had to nuke the OS.