Skip to content

Upgrade to Polkadot-SDK stable2506#817

Merged
fellowship-merge-bot[bot] merged 91 commits into
polkadot-fellows:mainfrom
acatangiu:bump-sdk-2506
Aug 7, 2025
Merged

Upgrade to Polkadot-SDK stable2506#817
fellowship-merge-bot[bot] merged 91 commits into
polkadot-fellows:mainfrom
acatangiu:bump-sdk-2506

Conversation

@acatangiu

@acatangiu acatangiu commented Jul 16, 2025

Copy link
Copy Markdown
Contributor

This brings in stable2506 Polkadot SDK, and integrates many new features.

Integrated breaking changes to be verified by the original authors:

@acatangiu acatangiu marked this pull request as draft July 16, 2025 16:27
@acatangiu acatangiu changed the title [WIP] Bump repo dependencies to Polkadot-SDK stable2506 [WIP] Upgrade to Rust 1.88 and Polkadot-SDK stable2506 Jul 17, 2025
@acatangiu

Copy link
Copy Markdown
Contributor Author

@brenzi please help with encointer dependencies, we need new version of the encointer pallets and primitives also based on stable2506

@alexggh

alexggh commented Aug 1, 2025

Copy link
Copy Markdown
Contributor

@alexggh @alindima can one of you help with this failing test in CI?

The following 1 benchmarks failed:
- runtime_parachains :: disputes :: slashing::report_dispute_lost_unsigned
Error: Input("1 benchmarks failed")
Error: Process completed with exit code 1.

@Overkillus, @ordian: Any idea ?

@bkontur

bkontur commented Aug 1, 2025

Copy link
Copy Markdown
Contributor

@alexggh @alindima can one of you help with this failing test in CI?

The following 1 benchmarks failed:
- runtime_parachains :: disputes :: slashing::report_dispute_lost_unsigned
Error: Input("1 benchmarks failed")
Error: Process completed with exit code 1.

@Overkillus, @ordian: Any idea ?

https://github.com/polkadot-fellows/runtimes/actions/runs/16673725543/job/47205674825?pr=817#step:10:107

2025-08-01T14:38:52.622374Z ERROR polkadot_sdk_frame::benchmark::pallet: Benchmark runtime_parachains :: disputes :: slashing::report_dispute_lost_unsigned failed: InvalidKeyOwnershipProof  

Comment thread relay/kusama/src/lib.rs Outdated
Comment thread relay/polkadot/src/lib.rs Outdated
Comment thread system-parachains/asset-hubs/asset-hub-polkadot/src/xcm_config.rs Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread CHANGELOG.md Outdated
Comment thread system-parachains/asset-hubs/asset-hub-polkadot/src/xcm_config.rs Outdated
Comment thread system-parachains/asset-hubs/asset-hub-polkadot/src/xcm_config.rs Outdated
acatangiu and others added 2 commits August 5, 2025 11:00
Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>

// see the `FEE_BOOST_PER_MESSAGE` constant to get the meaning of this value
pub PriorityBoostPerMessage: u64 = 182_044_444_444_444;
pub PriorityBoostPerMessage: u64 = 328_162_135_442_412;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks like a big increase?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

This is coming from doubling the POV size. It is only a relayer tx priority boost so I believe it is ok.

more details here paritytech/polkadot-sdk#5884 (comment)

@alexggh

alexggh commented Aug 6, 2025

Copy link
Copy Markdown
Contributor

@alexggh @alindima can one of you help with this failing test in CI?

The following 1 benchmarks failed:
- runtime_parachains :: disputes :: slashing::report_dispute_lost_unsigned
Error: Input("1 benchmarks failed")
Error: Process completed with exit code 1.

@Overkillus, @ordian: Any idea ?

I looked a bit at this benchmark, first the benchmarks seems to be ok on polkadot-sdk with the westend runtime, so I would presume there must be something from the polkadot runtime configuration, I did some debugging and the proof seems to be indeed invalid.

The reason the proof is invalid is that T::FullIdentification for test validators seems to be changing between the moment they get snapshotted at the beginning of the session here: https://github.com/paritytech/polkadot-sdk/blob/cf5a24ecc5802ecf78d943f9723b6f4ccdc0ddfa/substrate/frame/session/src/historical/mod.rs#L202

And the moment we generate the proof in the benchmark here: https://github.com/paritytech/polkadot-sdk/blob/cf5a24ecc5802ecf78d943f9723b6f4ccdc0ddfa/substrate/frame/session/src/historical/mod.rs#L345.

Then proof fails to check because it has a different root than the one used here: https://github.com/paritytech/polkadot-sdk/blob/cf5a24ecc5802ecf78d943f9723b6f4ccdc0ddfa/substrate/frame/session/src/historical/mod.rs#L374.

@Ank4n you seem to have been touching last this benchmark, https://github.com/paritytech/polkadot-sdk/blob/cf5a24ecc5802ecf78d943f9723b6f4ccdc0ddfa/polkadot/runtime/parachains/src/disputes/slashing/benchmarking.rs#L88, any chance this was something to do with the new staking changes ?

@Ank4n

Ank4n commented Aug 6, 2025

Copy link
Copy Markdown
Contributor

@alexggh @alindima can one of you help with this failing test in CI?

The following 1 benchmarks failed:
- runtime_parachains :: disputes :: slashing::report_dispute_lost_unsigned
Error: Input("1 benchmarks failed")
Error: Process completed with exit code 1.

@Ank4n you seem to have been touching last this benchmark, https://github.com/paritytech/polkadot-sdk/blob/cf5a24ecc5802ecf78d943f9723b6f4ccdc0ddfa/polkadot/runtime/parachains/src/disputes/slashing/benchmarking.rs#L88, any chance this was something to do with the new staking changes ?

Could you update the following? I believe it will fix the error.

type FullIdentificationOf = pallet_staking::DefaultExposureOf<Runtime>.

@Overkillus

Copy link
Copy Markdown
Contributor

type FullIdentificationOf = pallet_staking::DefaultExposureOf<Runtime>

That seemed to fix it. I assume this should be added to both Kusama and Polkadot RLCs. All benches run correctly now after testing the fix locally.

@acatangiu

Copy link
Copy Markdown
Contributor Author

type FullIdentificationOf = pallet_staking::DefaultExposureOf<Runtime>

That seemed to fix it. I assume this should be added to both Kusama and Polkadot RLCs. All benches run correctly now after testing the fix locally.

You can open a PR against this branch on my fork to get the fix in. Otherwise I will push it myself later tomorrow

@acatangiu

Copy link
Copy Markdown
Contributor Author

/merge

@fellowship-merge-bot fellowship-merge-bot Bot enabled auto-merge (squash) August 7, 2025 09:04
@fellowship-merge-bot

Copy link
Copy Markdown
Contributor

Enabled auto-merge in Pull Request

Available commands
  • /merge: Enables auto-merge for Pull Request
  • /merge cancel: Cancels auto-merge for Pull Request
  • /merge help: Shows this menu

For more information see the documentation

@acatangiu

Copy link
Copy Markdown
Contributor Author

/cmd fmt

@github-actions

github-actions Bot commented Aug 7, 2025

Copy link
Copy Markdown

Command "fmt" has started 🚀 See logs here

@github-actions

github-actions Bot commented Aug 7, 2025

Copy link
Copy Markdown

Command "fmt" has failed ❌! See logs here

@fellowship-merge-bot fellowship-merge-bot Bot merged commit d6c5bd3 into polkadot-fellows:main Aug 7, 2025
61 checks passed
@github-project-automation github-project-automation Bot moved this from Review to Done in Runtime releases Aug 7, 2025
@acatangiu acatangiu deleted the bump-sdk-2506 branch November 7, 2025 19:01
@acatangiu acatangiu restored the bump-sdk-2506 branch November 7, 2025 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.