-
Notifications
You must be signed in to change notification settings - Fork 116
Update to polkadot v0.9.39 #4705
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
6f56afc to
9712c6d
Compare
|
Integration test failing: edit: |
compiling now requires at least rustc 1.66.0
runtime weights need to be adjusted for fee/weight failing tests
|
I should mention that the new version should be 2002 and not 3000 |
dobertRowneySr
left a comment
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.
I left a few questions, but overall seems very good
| context: . | ||
| file: joystream-node.Dockerfile | ||
| # arm64 cross compiling takes longer than 6h, so we only build for amd64 | ||
| # platforms: linux/amd64,linux/arm64 |
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.
| # platforms: linux/amd64,linux/arm64 | |
| # platforms: linux/amd64 |
Since you said "only amd64" above.
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.
The line is already commented out, but left it for reference if we want to add it back.
It might be better to drop this whole workflow and improve joystream-node-docker.yml which deploys two worker machines on AWS (amd64 and arm64) to build natively for each platform arch have the ansible playbook build for all the runtime profiles.
| - name: Build | ||
| env: | ||
| WASM_BUILD_TOOLCHAIN: nightly-2022-05-11 | ||
| WASM_BUILD_TOOLCHAIN: nightly-2022-11-15 |
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.
Was this toolchain ver. recommended by substrate?
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 the nightly version at time the version was released
https://github.com/paritytech/polkadot/releases/tag/v0.9.39-rc6
| yarn cargo-checks && yarn cargo-build | ||
| ./target/release/call-sizes | ||
| if: env.GIT_DIFF | ||
| - name: OnRuntimeUpgrade (try-runtime) |
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.
This make the runtime-upgrade in the network tests obsolete, if I correctly understood the try runtime feature.
Should we drop the checks using the fork-off and move them to the pre/post hooks in the OnRuntimeUpgrade impl.?
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.
That's a good point.
There might still be some use for the runtime upgrade integration tests to see how it affects the query-node, storage and distributor nodes during an upgrade?
| # https://doc.rust-lang.org/rustc/linker-plugin-lto.html | ||
| lto = "fat" | ||
| # https://doc.rust-lang.org/rustc/codegen-options/index.html#codegen-units | ||
| codegen-units = 1 |
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.
Nice, where did you get the values from?
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.
From substrate/Cargo.toml https://github.com/paritytech/substrate/blob/31491fa24164b1cc9fffd5f07f06f41c8fef437d/Cargo.toml#L376
runtime/src/utils.rs
Outdated
| let len_fee = | ||
| <Runtime as pallet_transaction_payment::Config>::LengthToFee::weight_to_fee(&length); | ||
| let len_fee = <Runtime as pallet_transaction_payment::Config>::LengthToFee::weight_to_fee( | ||
| &Weight::from_ref_time(length), |
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.
| &Weight::from_ref_time(length), | |
| &Weight::from_parts(length, 0u64), |
I did some research and this function will be deprecated: https://paritytech.github.io/substrate/master/sp_weights/struct.Weight.html#method.from_ref_time
The suggestion is what they recommend
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.
Updated in 51fb763
|
I updated the PR from latest master branch. |
yes it has already been modified to 2002. |
Implements #4704
Changes:
50cf239147a6f569e563bcadec6c7a1c5ad5c67e3000and joystream-node versiondouble_map::remove_prefix(), shoulduse clear_prefix()instead - Supressed warningreactivate_pending_constitutionality_proposals()andremove_proposal_data()ss58-registryto include joystream address prefix. Our changes are included and published in crates.iopallet_staking::migrations::v10::MigrateToV10<Runtime>(from V7_0_0)pallet_staking::migrations::v11::MigrateToV11<Runtime,VoterList,StakingMigrationV11OldPallet>andpallet_staking::migrations::v12::MigrateToV12<Runtime>pallet_multisig::migrations::v1::MigrateToV1<Runtime>pallet_election_provider_multi_phase::migrations::v1::MigrateToV1<Runtime>andpallet_balances::migration::MigrateToTrackInactive<Runtime, xcm_config::CheckAccount>pallet_balances::migration::ResetInactive<Runtime>"We need to apply this migration again, because ResetInactive resets the state again."
pallet_balances::migration::MigrateToTrackInactive<Runtime, xcm_config::CheckAccount>pallet_staking::migrations::v13::MigrateToV13<Runtime>pallet_grandpa::migrations::CleanupSetIdSessionMap<Runtime>try-runtimecommand feature to the node, and build withtry-runtimefeature flag.Testing:
NextFeeMultiplierOnEmpty() -> 1so it is not a problem and no migration is required.Package Versioning:
Misc Fixes:
DefaultGlobalWeeklyNftLimit,DefaultChannelDailyNftLimit&DefaultChannelWeeklyNftLimit#4726TBD:
Optional:
frame_support::benchmarkingtoframe_benchmarking::v2paritytech/substrate#13235┆Issue is synchronized with this Asana task by Unito