-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fix try-runtime build and add missing migrations #296
Conversation
} | ||
|
||
fn migrate(&self, _available_weight: Weight) -> Weight { | ||
cumulus_pallet_xcmp_queue::migration::Migration::<T>::on_runtime_upgrade() |
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.
do we know for certain this puts the v3 on the pallet?
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.
because we probably need to set v2 first before doing this on_runtime_upgrade
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.
Yes, even if onchain is v1, it applies first the migration to v2 and immediately after the migration to v3 https://github.com/paritytech/polkadot-sdk/blob/master/cumulus/pallets/xcmp-queue/src/migration.rs#L36C1-L46C4
Can you merge master? I just merged a big PR that includes migrations, so there will be conflicts. |
@tmpolaczyk done |
try-runtime
now fails if there's a mismatch between a pallet's latest vs onchain versions. This flaggedPolkadotXcm
andXcmpQueue
from live dancebox.Missing migrations has been added