We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Reported here https://substrate.stackexchange.com/questions/10351/try-runtime-failed-to-generate-compact-proof-trieerrorinvalidstateroot and also impacts Asset Hub Kusama main branch.
main
Calling into https://github.com/paritytech/polkadot-sdk/blob/4ca193f88b55dc9b12d7a586113f9db192e1bdd8/substrate/primitives/trie/src/storage_proof.rs#L103 when calculating the PoV can return an error when the runtime differs in a particular way relative to the runtime the snapshot was generated from.
To debug, can bisect the Fellowship Runtime repo commit history starting from v1.0.1 to see exactly which change caused this issue.
v1.0.1
The text was updated successfully, but these errors were encountered:
TrieError(InvalidStateRoot(...))
Simply an error when the PoV is empty e.g. due to Migrations tuple being empty.
Sorry, something went wrong.
Fix TrieError(InvalidStateRoot(...)) error log when runtime upgrade…
7abe31b
… PoV is empty (#77) Closes #76
liamaharon
Successfully merging a pull request may close this issue.
Reported here https://substrate.stackexchange.com/questions/10351/try-runtime-failed-to-generate-compact-proof-trieerrorinvalidstateroot and also impacts Asset Hub Kusama
main
branch.Calling into https://github.com/paritytech/polkadot-sdk/blob/4ca193f88b55dc9b12d7a586113f9db192e1bdd8/substrate/primitives/trie/src/storage_proof.rs#L103 when calculating the PoV can return an error when the runtime differs in a particular way relative to the runtime the snapshot was generated from.
To debug, can bisect the Fellowship Runtime repo commit history starting from
v1.0.1
to see exactly which change caused this issue.The text was updated successfully, but these errors were encountered: