Skip to content

Upgrade to latest polkadot-sdk@1.5 release#137

Merged
bkchr merged 59 commits into
polkadot-fellows:mainfrom
bkontur:bko-bump-to-1.5
Feb 14, 2024
Merged

Upgrade to latest polkadot-sdk@1.5 release#137
bkchr merged 59 commits into
polkadot-fellows:mainfrom
bkontur:bko-bump-to-1.5

Conversation

@bkontur
Copy link
Copy Markdown
Contributor

@bkontur bkontur commented Jan 9, 2024

Attached result of cargo upgrade -v --pinned --incompatible cargo-upgrade-version-bump.log

E.g.: frame-support from 25.0.0 to 27.0.0

Note: Encointer was not upgraded (because its pallet references polkadot@1.3.0 release).

TODO

Closes: #113

@bkontur
Copy link
Copy Markdown
Contributor Author

bkontur commented Jan 13, 2024

@bkchr @ggwpez guys, any idea what is wrong here?

error: failed to run custom build command for `asset-hub-kusama-runtime v1.0.0 (/home/runner/work/runtimes/runtimes/system-parachains/asset-hubs/asset-hub-kusama)`
Caused by:
  process didn't exit successfully: `/home/runner/work/runtimes/runtimes/target/release/build/asset-hub-kusama-runtime-c709c9b8e18d4c08/build-script-build` (exit status: 1)
  --- stderr
  Cannot compile the WASM runtime: no standard library sources found!
  You can install them with `rustup component add rust-src` if you're using `rustup`.
warning: build failed, waiting for other jobs to finish...
error: failed to run custom build command for `bridge-hub-kusama-runtime v1.0.0 (/home/runner/work/runtimes/runtimes/system-parachains/bridge-hubs/bridge-hub-kusama)`
Caused by:
  process didn't exit successfully: `/home/runner/work/runtimes/runtimes/target/release/build/bridge-hub-kusama-runtime-c9ab234e71cf4721/build-script-build` (exit status: 1)
  --- stderr
  Cannot compile the WASM runtime: no standard library sources found!
  You can install them with `rustup component add rust-src` if you're using `rustup`.
Error: Process completed with exit code 101.

I just see that this error message is coming from here.

I thought it is related to the Fetch cache step error:

Warning: Error parsing Cargo.toml manifest, fallback to caching entire file: Error: Invalid TOML document: expected key-value, found comma

123:  serde_json = "1.0.111"
124:  remote-externalities = { package = "frame-remote-externalities" , version = "0.34.0" }

but it is not.

Locally it works (I know, I know...), maybe I missed something to port, will investigate Monday.

@bkchr
Copy link
Copy Markdown
Contributor

bkchr commented Jan 13, 2024

@bkontur change the stable toolchain installation to use the default profile. We need rust-src to be installed.

@bkontur
Copy link
Copy Markdown
Contributor Author

bkontur commented Jan 13, 2024

@bkontur change the stable toolchain installation to use the default profile. We need rust-src to be installed.

@bkchr ok, cool, thank you, back in the game, just adding rust-src to stable components with minimal profile works.

@ggwpez
Copy link
Copy Markdown
Member

ggwpez commented Jan 13, 2024

I thought it is related to the Fetch cache step error:

It should fix on the next update: Swatinem/rust-cache#172 (comment)

Comment thread relay/kusama/src/lib.rs
Comment thread relay/kusama/src/lib.rs
Comment thread relay/polkadot/src/lib.rs
@ggwpez ggwpez self-requested a review January 13, 2024 13:52
@bkontur bkontur force-pushed the bko-bump-to-1.5 branch 2 times, most recently from 69b9a5e to 01953fd Compare January 14, 2024 22:42
@bkontur
Copy link
Copy Markdown
Contributor Author

bkontur commented Jan 15, 2024

@ggwpez should we add DMP migrations (UndeployDmpQueue, DeleteDmpQueue) from here also?

@ggwpez
Copy link
Copy Markdown
Member

ggwpez commented Jan 16, 2024

@ggwpez should we add DMP migrations (UndeployDmpQueue, DeleteDmpQueue) from here also?

Its a two step process, first we do a runtime upgrade without them and then in the next one we add these migrations to delete the DmpQueue.
It is also not critical if it happens later since the pallet is already defunc.
PS: I cant find those migrations in the code-base 😅 wtf

@Ank4n
Copy link
Copy Markdown
Contributor

Ank4n commented Jan 17, 2024

pallet-staking bump >= 26 will introduce a paged exposure feature that will break some dapps if they have not integrated the changes. Is it possible to upgrade only Kusama and have it running only on Kusama for a while before upgrading Polkadot? cc: @jakoblell

https://forum.polkadot.network/t/staking-update-paged-staking-reward-to-avoid-validator-oversubscription-issue-is-live-on-westend/5215

bkontur added a commit to paritytech/polkadot-sdk that referenced this pull request Feb 6, 2024
This should result as a patched `24.0.1` version for
https://crates.io/crates/pallet-nomination-pools/24.0.0.

Relates to: polkadot-fellows/runtimes#137

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Alexander Samusev <41779041+alvicsam@users.noreply.github.com>
Co-authored-by: Dónal Murray <donal.murray@parity.io>
Co-authored-by: Bastian Köcher <info@kchr.de>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: PG Herveou <pgherveou@gmail.com>
acatangiu added a commit to paritytech/polkadot-sdk that referenced this pull request Feb 12, 2024
This is a cherry-pick of
#3094 (patch to
`release-polkadot-v1.5.0`).

This should result as a patched `24.0.1` version for
https://crates.io/crates/pallet-nomination-pools/24.0.0.

Relates to: polkadot-fellows/runtimes#137

---------

---------

Signed-off-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Oliver Tale-Yazdi <oliver.tale-yazdi@parity.io>
Co-authored-by: Alexander Samusev <41779041+alvicsam@users.noreply.github.com>
Co-authored-by: Dónal Murray <donal.murray@parity.io>
Co-authored-by: Bastian Köcher <info@kchr.de>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: PG Herveou <pgherveou@gmail.com>
Co-authored-by: command-bot <>
@bkontur
Copy link
Copy Markdown
Contributor Author

bkontur commented Feb 13, 2024

Fellows, please review this bump.

The only thing missing is the failed check-migrations (Polkadot) job, but this will be automatically resolved when Polkadot@1.1.2 is enacted on February 19: link to referendum.

.iter()
.cloned()
.map(|k| (k, ASSET_HUB_POLKADOT_ED * 4096))
.map(|k| (k, ASSET_HUB_POLKADOT_ED * 4096 * 4096))
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.

intentional increase?

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.

These are just genesis configs for testing, so changing them is fine.

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.

yes, but still might affect tests, wanted to point in case of accidental change

Comment thread chain-spec-generator/src/system_parachains_specs.rs
);
}

// TODO: Encointer pallets does not have compatible `polkadot-sdk` versions,
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.

it can be very easy to forget to update this when something updated in constants. may be we should try to drop some dependancies from constant crates. Should we have at least an issue for thus?

Comment thread system-parachains/asset-hubs/asset-hub-polkadot/src/lib.rs
@bkontur bkontur mentioned this pull request Feb 14, 2024
9 tasks
Comment thread system-parachains/asset-hubs/asset-hub-kusama/src/lib.rs
@bkchr bkchr merged commit e5a723f into polkadot-fellows:main Feb 14, 2024
@bkontur bkontur deleted the bko-bump-to-1.5 branch February 14, 2024 15:16
bkchr pushed a commit that referenced this pull request Feb 27, 2024
Based on bump to
[`polkadot-sdk@1.5.0`](#137).

Attached result of `cargo upgrade -v --pinned --incompatible`
[cargo-upgrade-version-bump.log](https://github.com/polkadot-fellows/runtimes/files/14044160/cargo-upgrade-version-bump.log)

_Note: Encointer was not upgraded (because its pallet references
`polkadot@1.3.0` release)._

## ~~For reviewers~~

~~This PR is against `polkadot-fellows`'s main to bring it to the
fellows repo, but if you want to see a real diff relevant to the
`polkadot-sdk@1.6.0` update please check:
bkontur/runtimes@bko-bump-to-1.5...bkontur:runtimes:bko-bump-to-1.6.~~


## TODO

- [x] fix compilation
- [x] fix integration tests
- [x] fix benchmarks (also try them) - `collectives-polkadot` `payout`
- [ ] ~~Does not require a CHANGELOG entry~~
- [x] `warning: use of deprecated struct
`staging_xcm_builder::CurrencyAdapter`: Use `FungibleAdapter` instead`
- [ ] search for `TODO:(PR#159) change to FungibleAdapter` and/or wait
for paritytech/polkadot-sdk#3287
- [x] patch for `pallet-nomination-pools` migration fix
paritytech/polkadot-sdk#3093
- will be fixed here
#188 (comment)
- [x] patch for `xcm-executor` fix (for 1.6.0) e.g.
paritytech/polkadot-sdk#3174
- [x] check/fix coretime stuff for Kusama/Polkadot - search for `//
TODO:(PR#159)(PR#1694)` - see
[comment](#159 (comment))
- fixed by bkontur#3
- [x] check the
`MaxControllersInDeprecationBatch`https://github.com/polkadot-fellows/runtimes/pull/159/files#r1492361038
- [x] check `pallet_identity::Config` for Kusama and Polkadot
https://github.com/polkadot-fellows/runtimes/pull/159/files#r1492363866

---------

Signed-off-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>
Co-authored-by: Ross Bulat <ross@parity.io>
Co-authored-by: Alain Brenzikofer <alain@integritee.network>
Co-authored-by: eskimor <eskimor@no-such-url.com>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: fellowship-merge-bot[bot] <151052383+fellowship-merge-bot[bot]@users.noreply.github.com>
bkchr pushed a commit that referenced this pull request Mar 4, 2024
…chain (#174)

This PR does two things:
1) (tiny refactoring) adds `TRANSACTION_BYTE_FEE` constant to
`system-parachains-constants` crate. We are using the same value (`1 *
MILLICENTS`) across all chains, so it makes sense to move it there;
2) changes default value of governance-controlled
`XcmBridgeHubRouterByteFee` constant (which is used to cover the cost of
message delivery within the remote consensus) to use
`TRANSACTION_BYTE_FEE` of the bridged chain (also does 1:5/5:1
conversion). Since governance has not set value of this constant yet, we
are changing the default value here, in the code.

~The failing test is fixed by the #137, so it makes sense to merge this
PR only after #137~ Updated

---------

Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Kian Paimani <5588131+kianenigma@users.noreply.github.com>
fellowship-merge-bot Bot pushed a commit that referenced this pull request Mar 21, 2024
- [x] Adds asset hub and bridge hub to Kusama and Polkadot runtimes
- [x] based off #108 -
needs to be merged first
- [x] snowbridge crates needs to be published on crates.io - depends on
`polkadot-sdk 1.7.0`
- [x] MessageQueue Pallet is not configured on Kusama and Polkadot asset
hub - added in #137
- [x] `FeeManager` `handle_fee` misses reason, crate needs to be updated
I think

cc @vgeddes @alistair-singh @yrong @musnit

---------

Signed-off-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Ross Bulat <ross@parity.io>
Co-authored-by: claravanstaden <Cats 4 life!>
Co-authored-by: Alain Brenzikofer <alain@integritee.network>
Co-authored-by: eskimor <eskimor@no-such-url.com>
Co-authored-by: Adrian Catangiu <adrian@parity.io>
Co-authored-by: brenzi <brenzi@users.noreply.github.com>
Co-authored-by: joe petrowski <25483142+joepetrowski@users.noreply.github.com>
Co-authored-by: ron <yrong1997@gmail.com>
Co-authored-by: Svyatoslav Nikolsky <svyatonik@gmail.com>
Co-authored-by: Vincent Geddes <vincent.geddes@hey.com>
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.

Convert Some Treasury Configs to NeverEnsure Once v1.5.0 is Released