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
If the binary we're running differs in version from the one the sdk was developed against we can get the following error:
Provider("io error: warning: the fuel node version to which this provider is connected has a semver incompatible version from the one the SDK was developed against. Connected node version: 0.33.0+nightly.20240820.b1f2bf445a, supported version: 0.32.1. Response errors; Occurred untyped error: Attempting to load invalid wasm bytecode, version=7. Current version is `8`")
What this indicates is that we've specified the executor version of 7 while the native executor is 8. This triggers the core to try and heal this version mismatch by using a wasm executor. We don't provide any when starting the fuel-core binary and that causes fuel-core to error out.
I seem to recall that fuel-core had a flag to force the usage of the native executor.
The text was updated successfully, but these errors were encountered:
If the binary we're running differs in version from the one the sdk was developed against we can get the following error:
What this indicates is that we've specified the executor version of 7 while the native executor is 8. This triggers the core to try and heal this version mismatch by using a wasm executor. We don't provide any when starting the
fuel-core
binary and that causesfuel-core
to error out.I seem to recall that
fuel-core
had a flag to force the usage of the native executor.The text was updated successfully, but these errors were encountered: