Update deps from v0.9.22 to v0.9.26

[ghzlatarev]

Signed-off-by: Georgi Zlatarev georgi.zlatarev@manta.network

Description

closes: #719
closes: #623
closes: #659

Manta

• Bumps dependencies from v0.9.22 -> v0.9.26
• Disable beefy for inprocess relay chain node paritytech/cumulus#1382 + Pump the gossip engine while waiting for the BEEFY runtime pallet (memory leak fix) paritytech/substrate#11694 fixes the memory leak issue of v3.2.1
• Switch ORML dependencies to use branch instead of a commit and to use the main fork instead of ours
• For nimbus use our own fork's garandor/v0.9.26 branch as it is not in upstream yet
• For storage deletions use new clear with limit and cursor instead of the deprecated remove_all. Call clear until there's nothing more to clear or the cursor is not progressing Safe and sane multi-item storage removal paritytech/substrate#11490
• Configure cumulus_pallet_parachain_system's new CheckAssociatedRelayNumber type, which is supposed to find associated relay blocks to a parachain block, with an implementation that strictly increases the relay block between para blocks
• Removed ExportGenesisStateCommand and ExportGenesisWasmCommand as they are now defined in cumulus-client-cli Move ExportGenesisStateCommand and ExportGenesisWasmCommand to cumulus-client-cli paritytech/cumulus#1325
• Use New rpc api and implementation name Unify rpc api and implementation name paritytech/substrate#11469
• Use AccountIdConversion's renamed into_account to into_account_truncating function to explicitly refer to the fact that it will truncate larger types to fit into a smaller type Explicitly note that existing AccountIdConversion is truncating and add fallible try_into... paritytech/substrate#10719
• For min-xcm-fee we can now return option instead of u128::max for invalid value Distinguish when MinXcmFee is not registered and FeeNotEnough open-web3-stack/open-runtime-module-library#753
• Use EitherOfDiverse instead of deprecated EnsureOneOf. It can now distinguish between one or the other failing options Introduce EnsureOrigin::try_successul_origin paritytech/substrate#11558
• Add Event to pallet-transaction-payment Add Event to Pallet Transaction Payment paritytech/substrate#11618
• Configure the new SpendOrigin type of the Treasury to always fail. This would be used if we want to allow certain origins to spend configurable amounts directly from the treasury, without the approve procedure Several tweaks needed for Governance 2.0 paritytech/substrate#11124
• Add placeholder weight for the new spend extrinsic of Treasury until it is properly benchmarked in the new release PR.

Substrate:

• Full diff beween v0.9.22 and v0.9.26 paritytech/substrate@616d33e...e8a7d16
• Network sync refactoring (part 3) paritytech/substrate#11347
• serde::{Serialize, Deserialize} for BoundedVec paritytech/substrate#11314
• Make sure the commit hash is always of the same length in impl_version paritytech/substrate#11404
• More benchmark machine args paritytech/substrate#11428
• frame_support::pallet_prelude: reexport StorageVersion paritytech/substrate#11408
• Remove unnecessary RPC boxing paritytech/substrate#11434
• Explicitly note that existing AccountIdConversion is truncating and add fallible try_into... paritytech/substrate#10719
• generate_storage_alias: Rewrite as proc macro attribute paritytech/substrate#11387
• Return a successful response on repeated small block request paritytech/substrate#11429
• Allow to set the max supply for collection paritytech/substrate#11441
• trie: Optimize keys function paritytech/substrate#11457
• Switch to pooling copy-on-write instantiation strategy for WASM paritytech/substrate#11232
• Add Score to Bags List paritytech/substrate#11357
• RPC: Mark storage methods as blocking  paritytech/substrate#11459
• InMemoryBackend: Make it generic over the key hasher paritytech/substrate#11488
• Unify rpc api and implementation name paritytech/substrate#11469
• rpc servers CLI: add --max--subscriptions--per--connection + fix a few bugs paritytech/substrate#11461
• Make --dev listen by default on /ip4/0.0.0.0/tcp/30333 paritytech/substrate#11492
• Use API for pr-custom-review paritytech/substrate#11487
• Introduce #[pallet::call_index] attribute to dispatchables paritytech/substrate#11381
• Adjust maximum memory pages hard limit for the pooling instantiation strategy paritytech/substrate#11482
• Optimize offchain worker memory usage a bit.  paritytech/substrate#11454
• Fix Babe revert when last finalized block is a leaf paritytech/substrate#11500
• Fix node lookup on fork-tree after a warp-sync paritytech/substrate#11476
• Storage Layer for All FRAME Extrinsics paritytech/substrate#11431
• Fork-Tree import requires post-order DFS traversal paritytech/substrate#11531
• Safe and sane multi-item storage removal paritytech/substrate#11490
• Several tweaks needed for Governance 2.0 paritytech/substrate#11124
• Introduce EnsureOrigin::try_successul_origin paritytech/substrate#11558
• Sync: Improve major sync detection paritytech/substrate#11547
• Ranked Collective pallet paritytech/substrate#11548
• Introduce set function into storage maps paritytech/substrate#11564
• Introduce SubmitOrigin to Referenda pallet config paritytech/substrate#11567
• wasm-builder: Rerun the build if the generated file changed paritytech/substrate#11582
• Expose ValidatedTransaction from transaction pool paritytech/substrate#11588
• Fix one-by-off in BoundedSlice::try_from paritytech/substrate#11600
• Remove a max supply record on collection's destruction paritytech/substrate#11593
• Implement more IntoIter traits for bounded types paritytech/substrate#11616
• Improve inspection and generation of node keys paritytech/substrate#11525
• pallet alliance paritytech/substrate#11112
• Move bounded type definitions to sp-runtime paritytech/substrate#11645
• Implement PartialOrd and Ord on BoundedSlice and WeakBoundedVec paritytech/substrate#11655
• Allow nomination pools to chill + fix dismantle scenario paritytech/substrate#11426
• Properly implement Debug on bounded types paritytech/substrate#11659
• Implement Deref for BoundedSlice paritytech/substrate#11660
• grandpa: fix creation of justification with equivocating precommits in commit paritytech/substrate#11302
• Make it possible to disable RocksDB completely paritytech/substrate#11537
• Pump the gossip engine while waiting for the BEEFY runtime pallet (memory leak fix) paritytech/substrate#11694
• More robust grandpa revert procedure paritytech/substrate#11719
• Respect cargo offline env variable in wasm builder paritytech/substrate#11735
• pallet-beefy-mmr: add API for BEEFY Authority Sets paritytech/substrate#11406
• Avoid a duplicate block request when syncing from a fork paritytech/substrate#11094

Polkadot:

• Full diff beween v0.9.22 and v0.9.26 paritytech/polkadot@17c7b95...d878597
• Remove Job trait related code paritytech/polkadot#5600
• provisioner: remove utils::job usage paritytech/polkadot#5568
• Rename BagsList to VoterList and Add Score paritytech/polkadot#5463
• Switch to pooling copy-on-write instantiation strategy for WASM (companion for Substrate#11232) paritytech/polkadot#5337
• Nomination Pools: add MinPointsToBalance constant  paritytech/polkadot#5520
• Migrate some Pallets to Named Events paritytech/polkadot#5423
• feat: allow subsystems to send only declared messages, generate graphviz paritytech/polkadot#5314
• Revert approval voting paritytech/polkadot#5438
• Remove bridges subtree paritytech/polkadot#5752
• fix(staking miner): query latest state when comparing to already submitted solutions paritytech/polkadot#5744
• pvf: ensure enough stack space paritytech/polkadot#5712
• pvf: unignore terminates_on_timeout test paritytech/polkadot#5722
• Remove Kusama Nomination Pools Init paritytech/polkadot#5605
• Allow relay chain council to send XCMs paritytech/polkadot#5597

Cumuls:

• Full diff beween v0.9.22 and v0.9.26 paritytech/cumulus@ebdfbea...e43b8b8
• Adding integration tests paritytech/cumulus#1426
• add wss bootnodes to statemine/t chainspec paritytech/cumulus#1378
• Add event with XCM executor outcome, which includes weight fee paritytech/cumulus#1286
• Add event with XCM executor outcome, which includes weight fee paritytech/cumulus#1286
• Move ExportGenesisStateCommand and ExportGenesisWasmCommand to cumulus-client-cli paritytech/cumulus#1325
• Disable beefy for inprocess relay chain node paritytech/cumulus#1382
• Lower all Assets / NFT deposits by 10x paritytech/cumulus#1332
• Ensure relay chain block number strictly increases paritytech/cumulus#1280
• Statemint Should Not Recognise DOT Reserves paritytech/cumulus#1318
• use RuntimeDebug paritytech/cumulus#1306

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Linked to Github issue with discussion and accepted design OR have an explanation in the PR that describes this work.
• Added one line describing your change in <branch>/CHANGELOG.md
• Re-reviewed Files changed in the Github PR explorer.

Situational Notes:

• If adding functionality, write unit tests!
• If importing a new pallet, choose a proper module index for it, and allow it in BaseFilter. Ensure every extrinsic works from front-end. If there's corresponding tool, ensure both work for each other.
• If needed, update our Javascript/Typescript APIs. These APIs are officially used by exchanges or community developers.
• If modifying existing runtime storage items, make sure to implement storage migrations for the runtime and test them with try-runtime. This includes migrations inherited from upstream changes, and you can search the diffs for modifications of #[pallet::storage] items to check for any.
• If runtime changes, need to update the version numbers properly:
  • authoring_version: The version of the authorship interface. An authoring node will not attempt to author blocks unless this is equal to its native runtime.
  • spec_version: The version of the runtime specification. A full node will not attempt to use its native runtime in substitute for the on-chain Wasm runtime unless all of spec_name, spec_version, and authoring_version are the same between Wasm and native.
  • impl_version: The version of the implementation of the specification. Nodes are free to ignore this; it serves only as an indication that the code is different; as long as the other two versions are the same then while the actual code may be different, it is nonetheless required to do the same thing. Non-consensus-breaking optimizations are about the only changes that could be made which would result in only the impl_version changing.
  • transaction_version: The version of the extrinsics interface. This number must be updated in the following circumstances: extrinsic parameters (number, order, or types) have been changed; extrinsics or pallets have been removed; or the pallet order in the construct_runtime! macro or extrinsic order in a pallet has been changed. You can run the metadata_diff.yml workflow for help. If this number is updated, then the spec_version must also be updated
• Verify benchmarks & weights have been updated for any modified runtime logics

[Dengjianping]

Can you align the version of crates like scale-info and codec with polkadot?
Not sure they are aligned. But it's not that important.

[ghzlatarev]

scale-info

I think cargo resolves to a single compatible version or it won't compile.

[Garandor]

i don't think we should allow two L- labels. Something is either changed or added, not both.
@Apokalip can you pls fail your tool if a PR has multiple of these? Only L, multiple A or C labels can be allowed

[ghzlatarev]

i don't think we should allow two L- labels. Something is either changed or added, not both. @Apokalip can you pls fail your tool if a PR has multiple of these? Only L, multiple A or C labels can be allowed

Yeah, there are just abnormal amount of changes in these bump PRs, Neither label is appropriate on its own. Maybe make a new one ?

[Garandor]

i don't think we should allow two L- labels. Something is either changed or added, not both. @Apokalip can you pls fail your tool if a PR has multiple of these? Only L, multiple A or C labels can be allowed

Yeah, there are just abnormal amount of changes in these bump PRs, Neither label is appropriate on its own. Maybe make a new one ?

I see changed as a superset of added.
Added is a diff that doesn't remove/alter any existing lines - no breaking changers of previous behavior.

[Apokalip]

i don't think we should allow two L- labels. Something is either changed or added, not both. @Apokalip can you pls fail your tool if a PR has multiple of these? Only L, multiple A or C labels can be allowed

Yeah, there are just abnormal amount of changes in these bump PRs, Neither label is appropriate on its own. Maybe make a new one ?

I see changed as a superset of added. Added is a diff that doesn't remove/alter any existing lines - no breaking changers of previous behavior.

We can change labels as we want now. If you put 2 labels it will be added to both those labels. How do we want to handle that? It will not be hard to change either way

[Garandor]

We can change labels as we want now. If you put 2 labels it will be added to both those labels. How do we want to handle that? It will not be hard to change either way

IMO we should make it consistent and a CI error if more than one L- tag is present