Skip to content
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-stable2024012-2 #396

Merged
merged 23 commits into from
Feb 26, 2025
Merged

polkadot-stable2024012-2 #396

merged 23 commits into from
Feb 26, 2025

Conversation

clangenb
Copy link
Member

@clangenb clangenb commented Feb 25, 2025

Notes:

  • I did not notice this in the parachain upgrade, but the node and the api-client support now the Extrinsic V5. This is 100% backwards and forwards compatible, so no issues should arise.
  • We are in the nirvana when it comes to benchmarking. Some pallets use () weights other use weights that we created in 2022. Shall we just completely switch to using ()? Or we fix the benchmarks, which might be a 1 hour task, see How to handle the weights and benchmarks (re-generate or switch to substrate defaults)? #397.
  • I had to downgrade the srtool action, as the build failed for no apparent reason. Now we use the same version as the fellowship. So maybe there is something wrong with the newer version.

Comment on lines +17 to +21
pub type EncointerXt<Call> = UncheckedExtrinsic<
ExtrinsicAddress,
Call,
Signature,
GenericSignedExtra<CommunityCurrencyTip, Nonce>,
GenericTxExtension<CommunityCurrencyTip, Nonce>,
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With this update, we implicitly introduce the UncheckedExtrinsicV5. However, it is entirely backwards compatible, and should not introduce any errors. (The parachain will support the V5 too with the stable2412 update).


- name: Summary
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did this while debugging the srtool-build. It turns out that a downgrade is all that was needed XD.

Regardless, we could simplify here a bit as subwasm is included in srtool.

RUN apt update && apt install -yq jq netcat
RUN apt update && apt install -yq jq netcat ca-certificates
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Luckily, we test docker in CI too. After the upgrade, the node was complaining about missing root CAs in the docker.

@@ -61,7 +61,6 @@ sp-offchain = { workspace = true }
sp-runtime = { workspace = true }
sp-session = { workspace = true }
sp-staking = { workspace = true }
sp-std = { workspace = true }
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

substrate is deprecating sp-std and started to migrate to core and alloc instead.

@clangenb clangenb requested a review from brenzi February 26, 2025 07:47
Copy link
Member

@brenzi brenzi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, din't check very deeply

@clangenb clangenb merged commit 91e132f into master Feb 26, 2025
25 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants