-
Notifications
You must be signed in to change notification settings - Fork 14
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
Replace native execution. #521
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So you managed to sync the chain on Foucoco with this change? 🥹 Great find 🙏
@@ -188,16 +151,14 @@ where | |||
.default_heap_pages | |||
.map_or(DEFAULT_HEAP_ALLOC_STRATEGY, |h| HeapAllocStrategy::Static { extra_pages: h as _ }); | |||
|
|||
let wasm = WasmExecutor::builder() | |||
let executor = ParachainExecutor::builder() | |||
.with_execution_method(config.wasm_method) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Isn't the execution_method
field deprecated anyway? Or is it just the CLI field? I remember seeing warnings when starting the node.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, good call. We can remove this and get rid of the warning.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I checked this method and it seems that it is not for selecting Native/wasm, but rather how to instantiate the wasm. I think we should keep it.
But you're right that there is a warning for the --execution
flag, which now makes even less sense to have. I'll try to find a way to remove it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay understood.
@@ -188,16 +151,14 @@ where | |||
.default_heap_pages | |||
.map_or(DEFAULT_HEAP_ALLOC_STRATEGY, |h| HeapAllocStrategy::Static { extra_pages: h as _ }); | |||
|
|||
let wasm = WasmExecutor::builder() | |||
let executor = ParachainExecutor::builder() | |||
.with_execution_method(config.wasm_method) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay understood.
Fixes issue 518.
Context
Since the metadata-hash chain extension cannot be used with the native runtime execution, and it's use seems to be deprecated as well, we replace the use of
NativeElseWasmExecutor
and useWasmExecutor
directly.