- Jun 21, 2021
-
-
Shawn Tabrizi authored
* use `configuration::config()` for max bytes * Update integration_tests.rs * Update paras_registrar.rs * remove consts * add asserts for non-zero * more const clean up * cargo run --release --features=runtime-benchmarks -- benchmark --chain=kusama-dev --steps=50 --repeat=20 --pallet=runtime_common::paras_registrar --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/kusama/src/weights/runtime_common_paras_registrar.rs * cargo run --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=runtime_common::paras_registrar --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/runtime_common_paras_registrar.rs * add checks to `MAX_CODE_SIZE` * re-pot MAX_POV_SIZE * check pov limit in runtime * POV_BOMB_LIMIT multiplier * fix compile * Update configuration.rs * Update node/primitives/src/lib.rs * fix test Co-authored-by: Parity Bot <[email protected]>
-
Alexander Popiak authored
* export fungibles_adapter types * formatting
-
- Jun 20, 2021
-
-
ordian authored
-
ordian authored
* downgrade to debug * another thick log * bump spec versions in kusama, polkadot and westend again IV
-
André Silva authored
* support async selectchain * update Substrate Co-authored-by: parity-processbot <>
-
dependabot[bot] authored
Bumps [kvdb-rocksdb](https://github.com/paritytech/parity-common) from 0.11.0 to 0.11.1. - [Release notes](https://github.com/paritytech/parity-common/releases) - [Commits](https://github.com/paritytech/parity-common/compare/kvdb-rocksdb-v0.11.0...kvdb-rocksdb-v0.11.1) --- updated-dependencies: - dependency-name: kvdb-rocksdb 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>
-
asynchronous rob authored
* determine-new-blocks: cleaner genesis avoidance and tighter ancestry requests * don't make ancestry requests when asking for one block
-
- Jun 19, 2021
-
-
André Silva authored
* fix babe params * update Substrate Co-authored-by: parity-processbot <>
-
dependabot[bot] authored
Bumps [env_logger](https://github.com/env-logger-rs/env_logger) from 0.8.2 to 0.8.4. - [Release notes](https://github.com/env-logger-rs/env_logger/releases) - [Changelog](https://github.com/env-logger-rs/env_logger/blob/main/CHANGELOG.md) - [Commits](https://github.com/env-logger-rs/env_logger/compare/v0.8.2...v0.8.4) --- updated-dependencies: - dependency-name: env_logger 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>
-
ordian authored
* network-bridge: remove action_sink abstraction * another wtf * filter out event stream * Revert "filter out event stream" This reverts commit 63bd8f5de5b44d415dcb205e1b9fad8145200e06. * retain cleanup though
-
asynchronous rob authored
* guide: ChainApiMessage::BlockWeight * node: BlockWeight ChainAPI * fix compile issue * implement ChainApi::BlockWeight * add test for ChainApi::BlockWeight * update substrate Co-authored-by: André Silva <[email protected]>
-
Andreas Doerr authored
-
Shawn Tabrizi authored
-
Lldenaurois authored
* node/approval-voting: test for invalid validator index in assignments This commit adds a unit test to show that, currently, validator indexes greater than n_validators (or the length of the approvals bitvector) are counted in n_assignments. In the subsequent commit we will correct this behavior. * node/approval-voting: ignore invalid validator indexes in n_assignments This commit ignores any validator assignments whose index is beyond n_validators. Without this check, an improperly crafted assignment would be counted towards the approval. It still remains that n_assignments and count_no_shows inspect the number of validators and approvals, respectively. Ideally we would add greater safety around ensuring these two values cannot differ.
-
- Jun 18, 2021
-
-
ordian authored
* gossip-support: gossip topology * some fixes * handle view update for newly added gossip peers * fix neighbors calculation * fix test * resolve TODOs * typo * guide updates * spaces in the guide * sneaky spaces * hash randomness * address some review nits * use unbounded in bridge for subsystem msg
-
Kian Paimani authored
* Set staking limits * Set westend limits as well * Update runtime/kusama/src/lib.rs Co-authored-by: Gavin Wood <[email protected]> Co-authored-by: Gavin Wood <[email protected]>
-
dependabot[bot] authored
Bumps [derive_more](https://github.com/JelteF/derive_more) from 0.99.11 to 0.99.14. - [Release notes](https://github.com/JelteF/derive_more/releases) - [Changelog](https://github.com/JelteF/derive_more/blob/master/CHANGELOG.md) - [Commits](https://github.com/JelteF/derive_more/compare/v0.99.11...v0.99.14) --- updated-dependencies: - dependency-name: derive_more 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>
-
- Jun 17, 2021
-
-
asynchronous rob authored
-
Hernando Castano authored
-
Lldenaurois authored
* node/approval-voting: extract and test count_no_shows method This commit extracts no_show computation into a pure function so that it can be extensively unit tested. * node/approval-voting: ignore invalid validator indexes in count_no_show Previously indexes that were past the length of the approvals bitvector would contribute to the no_show count or the next_no_show value. This commit changes the behavior to ignore garbage values. * node/approval-voting: add comment for next_no_show adding clock_drift
-
ordian authored
* cleanup more tests and spaces * oops
-
Zeke Mostov authored
* Companion #9019 (max rpc payload override) * update Substrate Co-authored-by: parity-processbot <>
-
asynchronous rob authored
* high-level discussion of fork-choice and chain selection * notes on chain-selection subsystem * send `Approve` messages from approval-voting * remove references to candidate-selection * adjust grandpa voting rule docs * Update roadmap/implementers-guide/src/node/grandpa-voting-rule.md Co-authored-by: Lldenaurois <[email protected]> * Update roadmap/implementers-guide/src/protocol-chain-selection.md Co-authored-by: Lldenaurois <[email protected]> * Update roadmap/implementers-guide/src/protocol-chain-selection.md Co-authored-by: Lldenaurois <[email protected]> Co-authored-by: Lldenaurois <[email protected]>
-
Bastian Köcher authored
-
Shaun Wang authored
-
Shawn Tabrizi authored
* Add XCM Decode Limit of 256 * use `decode_all_*` * Update xcm/src/double_encoded.rs
-
Shawn Tabrizi authored
* Allow council to use scheduler * westend doesnt have council
-
- Jun 16, 2021
-
-
Shawn Tabrizi authored
-
asynchronous rob authored
* extract determine_new_blocks into a separate utility * rework docs
-
Lldenaurois authored
* node/approval_checking: break out filled_tranch_iterator method In the subsequent commit, we will begin to test this method in isolation. * node/approval-voting: fix tranche back-filling algorithm Previously, this algorithm would generate duplicate, empty entries for tranches (1..pre_end). This is caused because the initial value (0) for gap_end is treated as the end of a prior tranche that wasn't actually processed. The first pass thus would add (1..tranche) empty entries, in addition to the (0..pre_end) empty entries chained at the end of the method. This is fixed by using the current tranche as the gap_start for the first iteration, ensuring that the approval_entries_filled only produces entries in the range (pre_end..post_start). * Address feedback
-
André Silva authored
* bridges: update finality-grandpa * update Substrate Co-authored-by: parity-processbot <>
-
Bernhard Schuster authored
-
Shawn Tabrizi authored
-
Shawn Tabrizi authored
* update weight apis * update Substrate Co-authored-by: parity-processbot <>
-
Keith Yeung authored
* Remove Call part imports of the offences and authority discovery pallets * Remove non-existent Call enum variants * Move ValidateUnsigned impl to be under #[pallet::validate_unsigned] in claims pallet * Remove unused imports * Remove Call part import for randomness collective flip pallet * update Substrate Co-authored-by: parity-processbot <>
-
- Jun 15, 2021
-
-
asynchronous rob authored
* Drop guard for detecting stale approvals * address nits with different API
-
Shawn Tabrizi authored
* update apis * fix api * rename to `KillStorageResult` * update Substrate Co-authored-by: parity-processbot <>
-
- Jun 14, 2021
-
-
Martin Pugh authored
* bump spec_version and version * bump substrate * remove migrations * Revert "remove migrations" This reverts commit ceeab924d1cd5c2d3d05f24ab28315f0566f89d8. * remove stale migration for kusama + westend
-
André Silva authored
* implement dispute participation subsystem * guide: minor fix in dispute participation * Update node/core/dispute-participation/src/lib.rs Co-authored-by: Andronik Ordian <[email protected]> * dispute: add comments to participation logic * dispute-coordinator: fix test compilation * implementers-guide: update dispute participation * dispute-participation: add error for missing validation code * dispute-participation: add tests * Update node/core/dispute-participation/src/lib.rs Co-authored-by: Robert Habermeier <[email protected]> * guide: update overseer protocol dispute participation message * dispute-participation: remove duplication in tests Co-authored-by: Andronik Ordian <[email protected]> Co-authored-by: Robert Habermeier <[email protected]>
-
Shawn Tabrizi authored
-