* Format runtime version
ref #787
* Remove the counter in the misc changes
* Add pre-release information
* Save context as artifact
* Rococo naming and minor fixes
* WIP
* Show the list of high prio issues
* Minor fixes
* Fix workflow title
* Attempt to fix Element rendering issue
* Code block fix
This PR is a part of
https://github.com/paritytech/polkadot/issues/3211.
This PR prepares ground for the following runtime changes required for
PVF pre-checking. Specifically, we do several changes here:
1. We remove `validation_code_at` and `validation_code_hash_at`. Those
functions are not used. They were added in the early days with intent
to use it later but turned out that we do not need them.
2. We replace `validation_code_hash_at` with just `current_code_hash`
for the case of inclusion and candidate checking.
3. We also replace `last_code_upgrade` with a direct query into
`FutureCodeHash` and `UpgradeRestrictionSignal`. Those in conjunction
should replace the logic that was used for allowing/disallowing
upgrades. This requires special attention of the reviewers.
4. Then we remove the machinery required to support those queries.
Specifically the code related to `UseCodeAt`. We do not need it since
we do not answer the historical queries. However, we still leave all
the data on-chain. At some point we may clean it up, but that would
be needed to be done with a dedicated migration which can be done as
follow-up.
5. Some now irrelevant tests were removed and/or adapted.
* pallet-bags-list: Add `put_in_front_of` extrinsic
This PR adds the extrinsic `put_in_front_of` which allows the user to specify a `lighter` and `heavier` account within the same bag. The extrinsic will move `heavier` directly in front of `lighter`. The parameter names refer to the fact that `lighter` must have a lower `VoteWeight` then `heavier`.
In the ideal use case, where a user wants to improve the position of their account within a bag, the user would iterate the bag, starting from the head, and find the first node who's `VoteWeight` is less than theirs. They would then supply the `id` of the node as the `lighter` argument and their own `id` as the `heavier` argument.
* Test & Benchmarks
* Respect line width
* Remove List::put_in_fron_of tests; Remove AlreadyHigher error
* The dispatch origin for this call must be ...
* Add some periods
* Add back test to list module: put_in_front_of_exits_early_if_bag_not_found
* add test tests::pallet::heavier_is_head_lighter_is_not_terminal
* Cater for edge case of heavier being head
* Add ExtBuilder::add_aux_data; try to make some tests use simpler data
* Update frame/bags-list/src/list/tests.rs
* make insert_at_unchecked infallible
* Make it permissioned - only callable by heavier
* Add test cases for insert_at_unchecked
* Move counter update to insert_at; fix comments
* Address some feedback
* Make voteweight constructed with parameter_types
* Always set vote weight for Ids in build
* Add skip_genesis_ids
* Do not pass weight fn to List put_in_front_of
* Remove remants of CounterForListNodes
* fmt
* cargo run --quiet --release --features=runtime-benchmarks --manifest-path=bin/node/cli/Cargo.toml -- benchmark --chain=dev --steps=50 --repeat=20 --pallet=pallet_bags_list --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./frame/bags-list/src/weights.rs --template=./.maintain/frame-weight-template.hbs
* Delete messed up weights file
* Some place holder stuff so we can run bench in CI
* Fix
* cargo run --quiet --release --features=runtime-benchmarks --manifest-path=bin/node/cli/Cargo.toml -- benchmark --chain=dev --steps=50 --repeat=20 --pallet=pallet_bags_list --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./frame/bags-list/src/weights.rs --template=./.maintain/frame-weight-template.hbs
* Update frame/bags-list/src/list/mod.rs
Co-authored-by: Guillaume Thiolliere <gui.thiolliere@gmail.com>
* fmt
* Log + debug assert when refetching an Id
Co-authored-by: Parity Bot <admin@parity.io>
Co-authored-by: Guillaume Thiolliere <gui.thiolliere@gmail.com>
* grandpa: allow authority set hard forks to be forced
* grandpa: fix authority set hard forks in warp proof provider
* grandpa: make AuthoritySetHardFork public
* grandpa: extend comment
* Frame no longer needs to be mutable (refactoring artifact)
* Remove Contract/Tombstone deposit
* Add StorageMeter
* cargo fmt
* Fix weight annotation
* cargo run --quiet --release --features=runtime-benchmarks --manifest-path=bin/node/cli/Cargo.toml -- benchmark --chain=dev --steps=50 --repeat=20 --pallet=pallet_contracts --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./frame/contracts/src/weights.rs --template=./.maintain/frame-weight-template.hbs
* Simplify keep check for contract accounts
- Make sure that the "base deposit" for each contract >= ed
- Remove now obsolete checks when sneding away free balance
* Remove unused imports and functions
* Rename storage_limit to storage_deposit_limit
* cargo fmt
* Fix typo
Co-authored-by: Michael Müller <michi@parity.io>
* Finish up rename of storage_limit
* Fix rpc tests
* Make use of `StorageDepositLimitTooHigh`
* Add tests and fix bugs discovered by tests
* Add storage migration
* Don't use u128 in RPC
* Fix weight of migration
* Rename `endowment` to `value`
* Fix bug where contract couldn't get funded by a storage deposit
- Make sure that contract gets funded from deposits before value is transferred
- Don't reserve value at origin because otherwise funding isn't possible
- Just transfer free balance and reserve it after the transfer
- When refunding make sure that this refund can't dust the contract
- Can only happen after a runtime upgrade where costs where upped
- Add more tests
* Apply suggestions from code review
Co-authored-by: Andrew Jones <ascjones@gmail.com>
* Remove unused `fn storage_meter`
* Fix copy pasta doc error
* Import `MaxEncodeLen` from codec
* Beautify RPC trait bounds
* Add re-instrument behaviour to dispatchable doc
* Make sure a account won't be destroyed a refund after a slash
* Apply suggestions from code review
Co-authored-by: Andrew Jones <ascjones@gmail.com>
* Update `Storage::write` docs
* Improve doc
* Remove superflous conditional
* Typos
* Remove superflous clone (refactoring artifact)
* Apply suggestions from code review
Co-authored-by: Andrew Jones <ascjones@gmail.com>
Co-authored-by: Parity Bot <admin@parity.io>
Co-authored-by: Michael Müller <michi@parity.io>
Co-authored-by: Andrew Jones <ascjones@gmail.com>
* Consolidating test and production code
* Signing/verifying authority discovery records with PeerId
Unsigned records cannot be rejected yet, they just produce
a warning in the log.
* Upgrading to libp2p 0.40
* libp2p::identity and sp_core::crypto Ed25519 are compatible
* Rejecting authority records unsigned by peer id can be configured
* Fixes based on review comments
* No command-line argument needed
* info was still too much spam in the logs
* Added tests for both strict and loose validation
* Fixing based on review comments
* Pierre preferred a signing method
* Ooops, I need to slow down
* Update bin/node/cli/src/service.rs
* Reexport libp2p crypto used in sc-network
* Added proto3 compatibility tests. And import noise.
Co-authored-by: Bastian Köcher <bkchr@users.noreply.github.com>
* Adds support for returning a custom header from `validate_block`
This adds support for returning a custom header from `validate_block`. Before this, we always
returned the header of the block that was validated (and still do it by default). However, after
this pr it is possible to set a custom header or better custom head data that will be returned
instead from `validate_block`. This can be for example when a chain wants to fork.
* FMT
This adds support to the wasm-override feature to compare the spec_name. If the spec_name doesn't
match, a warning will be printed and the override will be ignored.
* Account for transaction priority when enforcing limits
* Improve `enforce_limits` comment
* Explanation comment on why comparison impl is not used for limit enforcement
Chevdor