-
Notifications
You must be signed in to change notification settings - Fork 2.6k
thread 'tokio-runtime-worker-1' panicked at 'Bad input data provided to execute_block', node/runtime/src/lib.rs:421:1 #1212
Comments
Hey @algys
Sounds like you didn't change the runtime version before compiling/uploading the new runtime. From the logs it appears that because of that the runtime update is not considered different and the native version is being executed. However, as the native version doesn't have that new parameter, it fails to execute the newly changed transactions. Please update the runtime version and try again on a fresh chain. If the error persists please feel free to reopen this ticket! |
You right! I didn't change the version before upgrade. But now I tried change version before upgrade on a fresh chain: When I change
Then I did change all runtime versions(on a fresh chain):
and got another different error:
Before both tests I wiped chain data and start on a fresh chain |
Thus, all you want to change is |
Ok, thank you, finally I understood, but problem still actual I incremented only
|
…ch#1212) * Fix for new Substrate * Fix * Remove Utility constraint in NonTransfer * Bump * Fixes * Allow limited utilities in proxy filters. * Fix * Add SudoBalances proxy restrictions
) * Add pieces reconstruction from the segment. * farmer: Add segment reconstruction from DSN. * Fix review comments. * farmer: Add missing piece reconstruction. * Fix incorrect shards creation, pieces do not have the same size as shards * Simplify and make code more idiomatic, some TODOs * Remove unnecessary methods and replace with simple properties * Rename enum variant forgotten previously * archiver: Add more piece reconstruction tests. --------- Co-authored-by: Nazar Mokrynskyi <nazar@mokrynskyi.com>
Thread panic error after upgrade runtime code via 'upgradeKey' method.
Reproduce steps:
cargo run -- --dev --chain local
logs:
full bt: link
The text was updated successfully, but these errors were encountered: