Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

use native executor when running fuel-core binary #1488

Closed
segfault-magnet opened this issue Aug 20, 2024 · 0 comments · Fixed by #1489
Closed

use native executor when running fuel-core binary #1488

segfault-magnet opened this issue Aug 20, 2024 · 0 comments · Fixed by #1489
Assignees
Labels
bug Something isn't working

Comments

@segfault-magnet
Copy link
Contributor

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.

@segfault-magnet segfault-magnet added the bug Something isn't working label Aug 20, 2024
@segfault-magnet segfault-magnet self-assigned this Aug 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant