Skip to content

Resolve conflicts#988

Merged
pandres95 merged 9 commits into
polkadot-fellows:pandres95-upgrade-to-stable2509from
Snowfork:clara-upgrade-to-stable2509
Nov 3, 2025
Merged

Resolve conflicts#988
pandres95 merged 9 commits into
polkadot-fellows:pandres95-upgrade-to-stable2509from
Snowfork:clara-upgrade-to-stable2509

Conversation

@claravanstaden

Copy link
Copy Markdown
Contributor

@clangenb there are a couple of Encointer errors:

error[E0599]: no function or associated item named `convert` found for struct `EncointerBalanceConverter` in the current scope
   --> /Users/claravanstaden/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/pallet-encointer-balances-20.2.1/src/impl_fungibles.rs:27:29
    |
27  |     EncointerBalanceConverter::convert(balance)
    |                                ^^^^^^^ function or associated item not found in `EncointerBalanceConverter`
    |
note: there are multiple different versions of crate `sp_runtime` in the dependency graph

RomarQ and others added 9 commits October 12, 2025 12:45
…nfig (polkadot-fellows#844)

**Depends on** paritytech/polkadot-sdk#9451
---

Based on PR paritytech/polkadot-sdk#1781 and
[PRDoc](https://github.com/paritytech/polkadot-sdk/blob/beb9030b249cc078b3955232074a8495e7e0302a/prdoc/1.9.0/pr_1781.prdoc#L29),
the new way for providing the single block migrations should be through
`SingleBlockMigrations` in `frame_system::Config`. Providing them from
`frame_executive::Executive` is still supported, but from what I
understood is or will be deprecated.

> `SingleBlockMigrations` this is the new way of configuring migrations
that run in a single block. Previously they were defined as last generic
argument of Executive. This shift is brings all central configuration
about migrations closer into view of the developer (migrations that are
configured in Executive will still work for now but is deprecated).

Will also open a PR on polkadot-sdk side, adding a deprecation warning.
<!-- Remember that you can run `/merge` to enable auto-merge in the PR
-->

<!-- Remember to modify the changelog. If you don't need to modify it,
you can check the following box.
Instead, if you have already modified it, simply delete the following
line. -->

- [x] Does not require a CHANGELOG entry

---------

Co-authored-by: GitHub Action <action@github.com>
Fixes BridgeHubPolkadot Snowbridge benchmarks leftover from:
polkadot-fellows#959 catched by the
test:
https://github.com/polkadot-fellows/runtimes/actions/runs/18527148143/job/52800544994

<!-- Remember that you can run `/merge` to enable auto-merge in the PR
-->

<!-- Remember to modify the changelog. If you don't need to modify it,
you can check the following box.
Instead, if you have already modified it, simply delete the following
line. -->

- [X] Does not require a CHANGELOG entry
Brings paritytech/polkadot-sdk#10051 to here, to
be made into a 1.9.3 release for Kusama.

Can be merged, but a 1.9.3 release should come only after we verify the
fix in westend.

---------

Co-authored-by: Dónal Murray <donalm@seadanda.dev>
Release 1.9.3 for KAH only.
FRAME "View Functions"
(paritytech/polkadot-sdk#216) support was
implemented and released in Polkadot SDK with
paritytech/polkadot-sdk#4722, but it was never
exposed on the System Chains' runtimes.

This PR adds the missing `execute_view_function()` to all System Chains'
Runtime APIs.
# Conflicts:
#	Cargo.lock
#	Cargo.toml
@claravanstaden claravanstaden mentioned this pull request Oct 23, 2025
2 tasks
@clangenb

clangenb commented Oct 24, 2025

Copy link
Copy Markdown
Contributor

The encointer errors are most certainly because of duplicate dep issues still, and I believe that the encointer crates are on the correct versions.

But if you believe everything is correct on your end, I can look into it.

Comment thread Cargo.lock
Comment on lines -1930 to +1933
"bp-header-chain",
"bp-messages",
"bp-polkadot-core",
"bp-runtime",
"bp-header-chain 0.23.0",
"bp-messages 0.23.0",
"bp-polkadot-core 0.23.0",
"bp-runtime 0.23.0",

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.

You are introducing many duplicate dependencies. Is this on purpose?

Comment thread Cargo.lock
"parity-scale-codec",
"scale-info",
"sp-core 38.1.0",
"sp-runtime 43.0.0",

@clangenb clangenb Oct 24, 2025

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.

I think it is not on purpose. For example: this new duplicate dependency uses the old sp-runtime v43.0.0, whereas the current one is supposed to be v44.0.0.

I believe encointer's error will go away once the duplicate sp-runtime dependency has been resolved, aka sp-runtime v43.0.0 has been completely eliminated from the workspace.

@pandres95 pandres95 merged commit 6a02332 into polkadot-fellows:pandres95-upgrade-to-stable2509 Nov 3, 2025
13 of 69 checks passed
@claravanstaden claravanstaden deleted the clara-upgrade-to-stable2509 branch November 4, 2025 11:28
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.

8 participants