-
Notifications
You must be signed in to change notification settings - Fork 6
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
chore: upgrade v1.14.0 #198
Conversation
…hore-polkadot-v1.10.0
…polkadot-v1.10.0' into chungquantin/chore-polkadot-v1.10.0
…polkadot-v1.11.0' into chungquantin/chore-polkadot-v1.11.0
Co-authored-by: Peter White <[email protected]>
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.
After comparing the runtime with the parachain template in the SDK on 1.14.
Runtime
- Missing pov reclaim signed extension (should have been added in 1.9)
Node
- ReclaimHostFunctions, should also have been added to 1.9.
@Daanvdplas The POV reclaim feature is not added to this upgrade on purpose because there was a problem as discussed. |
Could we add that in the description please? So that we have a reference to it |
As we discussed in the 1.10.0 upgrade PR: https://github.com/paritytech/polkadot-sdk/pull/5371/files to whether we should add back the POV reclaim. From my understanding, it is fair to say that we can add back the feature in this v1.14.0 upgrade because there is a PR to fix the feature in this version: https://github.com/paritytech/polkadot-sdk/pull/5371/files Hence, we can reimplement that for both |
There is also this migration: https://github.com/paritytech/polkadot-sdk/blob/946afaabd8244f1256f3aecff75e23c02937bd38/polkadot/xcm/pallet-xcm/src/migration.rs#L84 And this change in 1.13 (search for Would love to hear @al3mart opinion on both before putting it in. |
About the PoV reclaim feature I think we are OK to include it as part of this PR if we want to have it.
On |
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.
So close! Great job.
As this is the last PR in the upgrade to 1.14, we should make sure all migrations are added.
try-runtime says we need a migration for XcmpQueue and pallet-contracts.
- https://github.com/paritytech/polkadot-sdk/blob/master/cumulus/parachains/runtimes/contracts/contracts-rococo/src/lib.rs#L113
- https://github.com/paritytech/polkadot-sdk/blob/master/cumulus/parachains/runtimes/contracts/contracts-rococo/src/lib.rs#L116
[ERROR runtime::frame-support] XcmpQueue: On chain storage version StorageVersion(4) doesn't match in-code storage version StorageVersion(5).
[ERROR runtime::frame-support] Contracts: On chain storage version StorageVersion(15) doesn't match in-code storage version StorageVersion(16).
Let's go ahead and just add |
pallet_contracts::Migration<Runtime>,
cumulus_pallet_xcmp_queue::migration::v5::MigrateV4ToV5<Runtime>,
pallet_xcm::migration::MigrateToLatestXcmVersion<Runtime>,
cc: @Daanvdplas @al3mart @peterwht Before merging this PR, could you guys please help me to review this PR as well: #201 which fixes the integration tests. |
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.
LGTM!!! Glad to see this so close being done.
Status: ✅ Compiled and built successfully
paseo
topolkadot
runtimes #201Direct changes
RuntimeFreezeReason
: paritytech/polkadot-sdk@988103druntime
macroRelated changes
litep2p
to v0.6.0