You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fuels CLI uses the system binaries over the soon-to-be deprecated built-in binaries whenever the user has them installed. But in some cases, the version of the binaries expected by the SDK and the version of the binaries that the user has installed can be different. In such cases, the error message that the users see is not self-explanatory:
❯ pnpm fuels:dev
> template-nextjs@0.1.3 fuels:dev /Users/dhaiwat/code/dhaii
> fuels dev
Starting source 'fuel-core' node..
error: unexpected argument '--snapshot' found
Usage: fuel-core run --ip <IP> --port <PORT> --db-path <DB_PATH> --min-gas-price <MIN_GAS_PRICE> --consensus-key <CONSENSUS_KEY> <--poa-instant <INSTANT>>
For more information, try '--help'.
error: unexpected argument '--snapshot' found
Usage: fuel-core run --ip <IP> --port <PORT> --db-path <DB_PATH> --min-gas-price <MIN_GAS_PRICE> --consensus-key <CONSENSUS_KEY> <--poa-instant <INSTANT>>
For more information, try '--help'.
In such cases, we should log out an error message like so:
Error: fuels v0.84.0 is compatible with fuel-core v0.26.0, but you have fuel-core v0.24.0 installed.
(Maybe we can also add instructions for how they can install the specific compatible version)
The text was updated successfully, but these errors were encountered:
Dhaiwat10
changed the title
Log out a proper error message when there is a version mismatch between SDK and system fuel-core / forc binaries when running fuels dev
Handle system<>SDK binary version mismatch for fuels CLI
May 9, 2024
The
fuels
CLI uses the system binaries over the soon-to-be deprecated built-in binaries whenever the user has them installed. But in some cases, the version of the binaries expected by the SDK and the version of the binaries that the user has installed can be different. In such cases, the error message that the users see is not self-explanatory:In such cases, we should log out an error message like so:
(Maybe we can also add instructions for how they can install the specific compatible version)
The text was updated successfully, but these errors were encountered: