Execution aborted due to trap: wasm trap: wasm unreachable instruction executed
#7341
Comments
github-actions
bot
added
the
I10-unconfirmed
|
@volodymyrd looks like you mixed up the paraid? Did you used somewhere a different paraid than |
|
@bkchr No, I just follow the doc and generate the chain spec like this: Should I try a different paraid than 1000? |
|
No that looks correct. Can you please share more logs of your node. |
|
Hi, root@PGR9:~/parachain-template# polkadot-omni-node --chain ./chain_spec.json --dev |
|
I took the chain spec from from Then I ran the omni node build for It panics here: To confirm it, I did a half-baked: @bkchr I saw that you left a comment on this PR (which is between two releases) and it happens to be the place where it fails. I don't have enough capacity to understand why the revert helps and why omni-node keeps being mean to us without it. |
|
Thanks for the investigation and report! I reproduced this issue and provide a fix in #7451. After that has landed in master, omni-node 2412-1 will be compatible again with the dev chainspec from master. |
This PR will make omni-node dev-mode once again compatible with older runtimes. The changes introduced in #6825 changed constraints that are enforced in the runtime. For normal chains this should work fine, since we have real parameters there, like relay chain slots and parachain slots. For these manual seal parameters we need to respect the constraints, while faking all the parameters. This PR should fix manual seal in omni-node to work with runtime build before and after #6825 (I tested that). In the future, we should look into improving the parameterization here, possibly by introducing proper aura pre-digests so that the parachain slot moves forward. This will require quite a bit of refactoring on the manual seal node side however. Issue: #7453 Also, the dev chain spec in parachain template is updated. This makes it work with stable2412-1 and master omni-node. Once the changes here are backported and in a release, all combinations will work again. fixes #7341 --------- Co-authored-by: cmd[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
Can confirm, it works. |
|
it works for me, thanks! |
I try to set up a template, but when I start the omni node with the command polkadot-omni-node --chain ./chain_spec.json --dev, the node starts, but I see this error:
Inherent extrinsic returned unexpected error: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: wasm
unreachableinstruction executedWASM backtrace:
error while executing at wasm backtrace:
0: 0x30767a - parachain_template_runtime.wasm!rust_begin_unwind
1: 0xc17a - parachain_template_runtime.wasm!core::panicking::panic_fmt::hc77aef7e4c7c0bd4
2: 0x255fab - parachain_template_runtime.wasm!frame_support::storage::transactional::with_transaction::hc0d3b0de73ade971
3: 0x2c6898 - parachain_template_runtime.wasm!environmental::local_key::LocalKey::with::h6c003c05e7cd116f
4: 0xd24f2 - parachain_template_runtime.wasm!<parachain_template_runtime::RuntimeCall as frame_support::traits::dispatch::UnfilteredDispatchable>::dispatch_bypass_filter::h94a427eb3bf5cc3d
5: 0xcf566 - parachain_template_runtime.wasm!<parachain_template_runtime::RuntimeCall as sp_runtime::traits::Dispatchable>::dispatch::h8e87a075039c0e7b
6: 0xf74d6 - parachain_template_runtime.wasm!<sp_runtime::generic::checked_extrinsic::CheckedExtrinsic<AccountId,Call,Extra> as sp_runtime::traits::Applyable>::apply::hf803b97a1c0b84e3
7: 0x25f1d8 - parachain_template_runtime.wasm!frame_executive::Executive<System,Block,Context,UnsignedValidator,AllPalletsWithSystem,COnRuntimeUpgrade>::apply_extrinsic::h2ccce8eaf468136c
8: 0x26f7d4 - parachain_template_runtime.wasm!BlockBuilder_apply_extrinsic. Dropping.
2025-01-26 20:12:42 [Parachain] panicked at /Users/vova/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cumulus-pallet-parachain-system-0.17.1/src/lib.rs:263:6:
set_validation_data inherent needs to be present in every block!
2025-01-26 20:12:42 [Parachain] Consensus with no RPC sender encountered an error: Error at calling runtime api: Execution failed: Execution aborted due to trap: wasm trap: wasm
unreachableinstruction executedCan you help me understand what's wrong with my setup.
The text was updated successfully, but these errors were encountered: