- Jan 05, 2022
-
-
sandreim authored
* initial changes Signed-off-by:
Andrei Sandu <[email protected]> * fmt Signed-off-by:
Andrei Sandu <[email protected]> * remove file Signed-off-by:
Andrei Sandu <[email protected]> * Remove pallet Signed-off-by:
Andrei Sandu <[email protected]> * fix copyright year Signed-off-by:
Andrei Sandu <[email protected]> * Remove metric registration op Signed-off-by:
Andrei Sandu <[email protected]> * Register runtime metrics in client Signed-off-by:
Andrei Sandu <[email protected]> * fmt Signed-off-by:
Andrei Sandu <[email protected]> * fix build without `runtime-metrics` Signed-off-by:
Andrei Sandu <[email protected]> * reduce visibility Signed-off-by:
Andrei Sandu <[email protected]> * remove metric prefix logic, use hardcoded Signed-off-by:
Andrei Sandu <[email protected]> * fix Signed-off-by:
Andrei Sandu <[email protected]> * review feedback Signed-off-by:
Andrei Sandu <[email protected]> * Split CounterVec api so it doesn't need mutability Signed-off-by:
Andrei Sandu <[email protected]> * Const beautify Signed-off-by:
Andrei Sandu <[email protected]> * fix Signed-off-by:
Andrei Sandu <[email protected]> * Fix Signed-off-by:
Andrei Sandu <[email protected]> * fix docs Signed-off-by:
Andrei Sandu <[email protected]> * Merge web ui feedback. Co-authored-by:
Bastian Köcher <[email protected]> Co-authored-by:
Bastian Köcher <[email protected]>
-
Adrian Catangiu authored
Signed-off-by:
acatangiu <[email protected]>
-
Kian Paimani authored
* Fully enable bags-list pallet in polkadot runtime * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=polkadot-dev --steps=50 --repeat=20 --pallet=pallet_staking --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/polkadot/src/weights/ * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=kusama-dev --steps=50 --repeat=20 --pallet=pallet_staking --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/kusama/src/weights/ * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=pallet_staking --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/ Co-authored-by:
Parity Bot <[email protected]>
-
- Jan 04, 2022
-
-
ordian authored
-
ordian authored
* collator-protocol: add to reserved peers on every relay parent * bump collator slots from 25 to 100 * collator-protocol: reduce inactivity timeout from 24s to 5s * try to satisfy spellcheck * add connection log * fmt * bring a warn back * gather validators across all active leaves
-
Robert Klotzner authored
* Don't change rep on timeout in collator protocol. * Fix tests. * Fixes.
-
Zeke Mostov authored
-
- Jan 03, 2022
-
-
Martin Pugh authored
There have been some subtle changes to the release process since this document was last updated. This PR updates the RELEASE.md to reflect these changes.
-
Keith Yeung authored
* Set CurrentCodeHash before running some dispatchable benchmarks * Use insert instead of put * Actually hash the ValidationCode * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/runtime_parachains_paras.rs Co-authored-by:
Parity Bot <[email protected]>
-
Sergey Pepyakin authored
This is only a module structure change: the tests module was promoted to have its own file.
-
- Jan 02, 2022
-
-
dependabot[bot] authored
Bumps [quote](https://github.com/dtolnay/quote) from 1.0.10 to 1.0.14. - [Release notes](https://github.com/dtolnay/quote/releases) - [Commits](https://github.com/dtolnay/quote/compare/1.0.10...1.0.14 ) --- updated-dependencies: - dependency-name: quote dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by:
dependabot[bot] <[email protected]> Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
dependabot[bot] authored
* Bump pin-project from 1.0.8 to 1.0.9 Bumps [pin-project](https://github.com/taiki-e/pin-project) from 1.0.8 to 1.0.9. - [Release notes](https://github.com/taiki-e/pin-project/releases) - [Changelog](https://github.com/taiki-e/pin-project/blob/main/CHANGELOG.md) - [Commits](https://github.com/taiki-e/pin-project/compare/v1.0.8...v1.0.9 ) --- updated-dependencies: - dependency-name: pin-project dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by:
dependabot[bot] <[email protected]> * Update pin-project to fix compilation * Also bump the old ones Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by:
Bastian Köcher <[email protected]>
-
- Jan 01, 2022
-
-
Sergey Pepyakin authored
As was brought up in [here][og], we have some copy&paste comments. I fixed them and also took liberty of fixing some other places. Specifically, those that say "module" instead of contemporary "pallet". [og]: https://github.com/paritytech/polkadot/pull/4603#discussion_r776971291
-
Sergey Pepyakin authored
Motivation is to resolve [this TODO](https://github.com/paritytech/cumulus/blob/b9ba74892ad6199128a45703b89ff06f429be7fa/test/relay-sproof-builder/src/lib.rs#L73) eventually
-
- Dec 31, 2021
-
-
Sergey Pepyakin authored
Closes #3971 Read the linked issue. Apart from that, this addresses the concern raised in this [comment] by just adding a test. I couldn't find a clean way to reconcile a block number delay with a PVF voting TTL, so I just resorted to rely on the test. Should be fine for now. [comment]: https://github.com/paritytech/polkadot/pull/4457#discussion_r770517562
-
- Dec 30, 2021
-
-
Sergey Pepyakin authored
This just renames a member of `HostConfiguration` from validation_upgrade_frequency to -//-_cooldown. As was already pointed out in #4460 the existing name is a misnomer, the member actually represents a minimum time period between upgrades, which is neatly expressed by a word cooldown. I've been planning this rename already for some time and the term is already used in paras module: https://github.com/paritytech/polkadot/blob/1394b70d493a3b4bea7a9ae14af094081bc84456/runtime/parachains/src/paras.rs#L1568-L1574
-
- Dec 29, 2021
-
-
dependabot[bot] authored
Bumps [lru](https://github.com/jeromefroe/lru-rs) from 0.7.1 to 0.7.2. - [Release notes](https://github.com/jeromefroe/lru-rs/releases) - [Changelog](https://github.com/jeromefroe/lru-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/jeromefroe/lru-rs/compare/0.7.1...0.7.2 ) --- updated-dependencies: - dependency-name: lru dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by:
dependabot[bot] <[email protected]> Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
Sergey Pepyakin authored
* paras: add governance control dispatchables Adds a couple of functions for governance control for the paras module in the anticipation of PVF pre-checking enabling. Specifically, this commit adds a function for pre-registering a PVF that governance trusts enough. This function will come in handy in case there is a parachain that does not follow the GoAhead signal. That is, does not include https://github.com/paritytech/cumulus/pull/517 . This may be not an exhaustive list of the functions that may come in handy. Any suggestions to add more are welcome. * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=kusama-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/kusama/src/weights/runtime_parachains_paras.rs * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=polkadot-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/polkadot/src/weights/runtime_parachains_paras.rs * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/runtime_parachains_paras.rs * cargo run --quiet --release --features runtime-benchmarks -- benchmark --chain=rococo-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/rococo/src/weights/runtime_parachains_paras.rs Co-authored-by:
Parity Bot <[email protected]>
-
ordian authored
* add custom profiles and specify MSVR as 1.57 * fix host-perf-check command * use testnet profile for CI images * do not do lto for testnet profile * fix artifact path * test with testnet profile to reuse build artifacts * Revert "fix host-perf-check command" This reverts commit f1d15492204b8251685a97636cbb5a5f394f21da. * bump zombienet version Co-authored-by:
Javier Viola <[email protected]>
-
Sergey Pepyakin authored
This commit incorporates the changes made to the runtime in the following PRs: - https://github.com/paritytech/polkadot/pull/4408 - https://github.com/paritytech/polkadot/pull/4457 - https://github.com/paritytech/polkadot/pull/4540 - https://github.com/paritytech/polkadot/pull/4542 - https://github.com/paritytech/polkadot/pull/4581 Note that this PR does not include the description of the PVF pre-checker subsystem. This should be addressed within https://github.com/paritytech/polkadot/issues/4611 Co-authored-by:
sandreim <[email protected]>
-
Keith Yeung authored
* Use derive macro to generate XcmWeightInfo trait * Move the Weight type alias out of proc macro
-
dependabot[bot] authored
Bumps [proc-macro2](https://github.com/dtolnay/proc-macro2) from 1.0.34 to 1.0.36. - [Release notes](https://github.com/dtolnay/proc-macro2/releases) - [Commits](https://github.com/dtolnay/proc-macro2/compare/1.0.34...1.0.36 ) --- updated-dependencies: - dependency-name: proc-macro2 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by:
dependabot[bot] <[email protected]> Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
- Dec 28, 2021
-
-
sandreim authored
* Read me. Signed-off-by:
Andrei Sandu <[email protected]> * Add dashboards and readme Signed-off-by:
Andrei Sandu <[email protected]> * Update root readme Signed-off-by:
Andrei Sandu <[email protected]> * Add dashboard links in readme Signed-off-by:
Andrei Sandu <[email protected]> * updates Signed-off-by:
Andrei Sandu <[email protected]> * Updates Signed-off-by:
Andrei Sandu <[email protected]> * bump zombienet version Co-authored-by:
Javier Viola <[email protected]>
-
Sergey Pepyakin authored
* runtime-api: add validation_code_hash API This is the first step to close https://github.com/paritytech/polkadot/issues/4524 * collation-gen: don't hash validation code Closes https://github.com/paritytech/polkadot/issues/4524
-
Sergey Pepyakin authored
This is the first step to close https://github.com/paritytech/polkadot/issues/4524
-
Sergey Pepyakin authored
Closes #4248 Impose additional constraint on configuration consistency: `validation_upgrade_delay` should not be less than or equal to 1. See the original issue for more details.
-
Sergey Pepyakin authored
Setting zero as weight may be a source of problems. The problem is, a rogue validator can shove a lot of duplicated votes and thus fill a block with work that may well exceed the weight limit.
-
Sergey Pepyakin authored
As was suggested by Alexander Popiak [here][comment], this commit checks the consistency of the configuration. [comment]: https://github.com/paritytech/polkadot/pull/4420#discussion_r764796519
-
- Dec 27, 2021
-
-
sandreim authored
Signed-off-by:
Andrei Sandu <[email protected]>
-
Sergey Pepyakin authored
This commit refactors the consistency checks. Instead of each individual setter performs its checks locally, we delegate those checks to the already existing function `check_consistency`. This removes duplication and simplifies the logic. A motivating example of this one is the next PR in the stack that will introduce a check for a field, which validity depends on the validity of other two fields. Without this refactoring we will have to place a check not only to the field in question, but also to the other two fields so that if they are changed they do not violate consistency criteria. It's easy to imagine how this can go unwieldy with the number of checks. This also adds a test that verifies that the default chain spec host configuration is consistent.
-
ordian authored
* zombinet: fixed adder-collator image for the smoke test * update COL_IMAGE * bump zombienet version * try a different version Co-authored-by:
Javier Viola <[email protected]>
-
João Paulo Silva de Souza authored
Make check-dependent-* jobs only be executed in PRs instead of both PRs and master. Reason 1: The companion is not merged at the same time as the parent PR ([1](https://github.com/paritytech/parity-processbot/issues/347#issuecomment-994729950)), therefore the pipeline will fail on master since the companion PR is not yet merged in the other repository. This scenario is demonstrated by the pipeline of https://github.com/paritytech/substrate/commit/82cc3746450ae9722a249f4ddf83b8de59ba6e0d. Reason 2: The job can still fail on master due to a new commit on the companion PR's repository which was merged after `bot merge` happened, as demonstrated by the following scheme: 1. Parent PR is merged 2. Companion PR is updated and set to merge in the future 3. In the meantime a new commit is merged into the companion PR repository's master branch 4. The `check-dependent-*` job runs on master but, due to the new commit, it fails for unrelated reasons While "Reason 2" can be used as an argument against this PR, in that it would be useful to know if the integration is failing on master, "Reason 1" should be taken care of due to this inherent flaw of the current companion build system design.
-
ordian authored
-
ordian authored
* session_info: v2 + migration * use primitives::v2 * use polkadot_primitives::v2 * impl primitives::v2 * fix approval-voting tests * fix other tests * hook storage migration up * backwards compat (1) * backwards compat (2) * fmt * fix tests * FMT * do not reexport v1 in v2 * fmt * set storage version to 1 Co-authored-by:
Javier Viola <[email protected]>
-
- Dec 25, 2021
-
-
dependabot[bot] authored
Bumps [zstd](https://github.com/gyscos/zstd-rs) from 0.9.0+zstd.1.5.0 to 0.9.1+zstd.1.5.1. - [Release notes](https://github.com/gyscos/zstd-rs/releases) - [Commits](https://github.com/gyscos/zstd-rs/compare/0.9.0...0.9.1 ) --- updated-dependencies: - dependency-name: zstd dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by:
dependabot[bot] <[email protected]> Co-authored-by:
dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
Bastian Köcher authored
* changed Rococos epoch to 1h * Changed assigned_slots parameters to match ecosystem needs * Update rococo chain spec Co-authored-by:
Santi Balaguer <[email protected]>
-
- Dec 24, 2021
-
-
cheme authored
* merge master (do not compile) * fix * lock * update lock * Update to refactoring. * runtime version * fmt * remove trie patch * remove patch * No layout alias for bridge proof. * update depupdate depss * No switch until migration. * master lock * test * test * Revert "test" This reverts commit 57325ef73332bf4b054aa4a667bb716fcf8a0d89. * Revert "test" This reverts commit ce74d0e2062806f72c0e9e9ca07b14165f43521e. * rename feature * state version as parameter, use the feature only on runtimes. * update * update to state version in runtime * state version from storage * update lockfile for substrate Co-authored-by: parity-processbot <>
-
Robert Klotzner authored
-
- Dec 23, 2021
-
-
Bastian Köcher authored
The function `has_api` checks that the api + version matches, which isn't true anymore after bumping the version. The fix is to just compare the runtime api version being at least `1`.
-
Bastian Köcher authored
The runtime version check `runtime_version <= version` was wrong, it needs to be `>=`. Besides that the `WIDELY_DEPLOYED_API_VERSION` is removed. The runtime version is already cached, aka we don't always call into the runtime when requesting the runtime version. So, there is no need to "optimize" this.
-