-
Notifications
You must be signed in to change notification settings - Fork 84
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
Polkadot v1.1.0 #1756
Polkadot v1.1.0 #1756
Conversation
dc93db7
to
fb19264
Compare
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.
Looking really good, great job taming this beast! I have a bunch of questions. For a few things, I have posted them as Placeholder to check where these particular code paths went.
@@ -270,7 +270,7 @@ pub mod constants { | |||
pub const TRANSACTION_RECOVERY_ID: u64 = 42; | |||
|
|||
/// The safe XCM version of pallet-xcm, same as on relay chain | |||
pub const SAFE_XCM_VERSION: u32 = xcm::opaque::v2::VERSION; | |||
pub const SAFE_XCM_VERSION: u32 = staging_xcm::opaque::v2::VERSION; |
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.
FYI: I think we can switch to v3 by now but that would be out of scope of this PR.
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.
You're right. We can do after merging this 👍🏻
cargo run --release --features try-runtime try-runtime \ | ||
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 will break the try-runtime
CI. Since you pinged @gpmayorga already and try-runtime
being optional, I am fine with leaving this as is.
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 will break the try-runtime CI?
Mmm... you said that because we're not installing try-runtime
binary, right? Probably. I've tested locally but I have the tool 😆
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.
Can we add this as a tech-debt? In the CI job, I've seen some comment lines regarding this. So, probably, just uncommenting those makes this work.
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.
Since we are not really utilizing the CI right now, totally fine with this.
Thanks @wischli for your deep and detailed review 🙌🏻. Really appreciated |
@@ -272,7 +282,7 @@ pub type LocationToAccountId<RelayNetwork> = ( | |||
// Straight up local `AccountId32` origins just alias directly to `AccountId`. | |||
AccountId32Aliases<RelayNetwork, AccountId>, | |||
// Generate remote accounts according to polkadot standards | |||
cfg_primitives::xcm::HashedDescriptionDescribeFamilyAllTerminal<AccountId>, | |||
HashedDescription<AccountId, DescribeFamily<DescribeAllTerminal>>, |
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.
We had test covering the conversions made beforehand and can ensure that they stay the same, right?
* Modify AccountConverter types * fix some imports
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.
Soft approving this with the following TODO list
Best before merge
TBD
- Hardcode para id for gateway: Polkadot v1.1.0 #1756 (comment)
- Maybe revert removed
HashedDescription
tests: Polkadot v1.1.0 #1756 (comment)
Post merge
- Switch to dedicated
try-runtime
CLI: Polkadot v1.1.0 #1756 (comment) - Switch to
v3
as safe xcm version: Polkadot v1.1.0 #1756 (comment)
* fix: deprecate parachain CLI * chore: cleanup deprecated chain specs * fix: clippy
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.
Re-approving. Sorry, should have merged #1808 before
No worries! And thanks for the wrap-up comment! |
Description
Fixes #1734
Current work done
polkadot-sdk
with version1.1.0
.polkadot-sdk
dependenciescargo check
&cargo test
usingruntime-benchmarks
featureEvaluate this: UsedFixed upgrading to rust-1.78chainbridge
dependency from Use latest deps for Polkadot v1.1.0 chainbridge-substrate#15, which should be fixed/evaluatedEvaluate this: I've needed to point toFinally using the moonbeam forkpolkadot-evm
dependencies instead of themoonbeam-foundation
fork. There seems to be a lot of chaos with moonbeam dependencies. Ensure this is correct.lemunozm
). <= We should remove this fork in v1.3.0It seemsIt seems not related to this migration. Having the same message onpallet-ethereum
need itmain
. It seems it appears because they never set a VERSION.pallet_collator_selection