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

lib(runtime/wazero): next_key returned a key with no value at [] #3466

Closed
EclesioMeloJunior opened this issue Sep 4, 2023 · 1 comment · Fixed by #3473
Closed

lib(runtime/wazero): next_key returned a key with no value at [] #3466

EclesioMeloJunior opened this issue Sep 4, 2023 · 1 comment · Fixed by #3473

Comments

@EclesioMeloJunior
Copy link
Member

Describe the bug

  • Sync stalled after the log
2023-09-02T05:39:32Z CRITICAL target=frame_support::storage message=next_key returned a key with no value at [] ext_logging_log_version_1 pkg=runtime module=wazero

image

@EclesioMeloJunior
Copy link
Member Author

By using the polkadot/crowdloan pallet I could simulate the error using the ChildTriePrefixIterator which returns an iterator that goes over the ext_default_child_storage_next_key_version_1

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant