- Aug 18, 2022
-
-
Bastian Köcher authored
* Switch to Substrate branch * Make everything compile * Revert "Switch to Substrate branch" This reverts commit cbbab7431a07cfd645428a9f4c130362a8e7588b. * Remove stuff * More fixes * Fix branch * Update Substrate * FMT
-
- Aug 17, 2022
-
-
Alexander Samusev authored
* [WIP] Playground for check-runtime-migration * add condition * fix syntax * enable pipeline * uncomment needs * change label name to code label
-
- Aug 16, 2022
-
-
Shawn Tabrizi authored
* initial stuff * make copy data from kusama * Update runtime/kusama/src/governance/old.rs Co-authored-by: Bastian Köcher <[email protected]> * Update runtime/kusama/src/governance/mod.rs Co-authored-by: Bastian Köcher <[email protected]> Co-authored-by: Bastian Köcher <[email protected]>
-
Joakim Nyman authored
-
Robert Klotzner authored
-
Robert Klotzner authored
* Don't request votes if there is nothing to request. * Add trace log
-
Robert Klotzner authored
* Don't import backing statements directly into the dispute coordinator. This also gets rid of a redundant signature check. Both should have some impact on backing performance. In general this PR should make us scale better in the number of parachains. Reasoning (aka why this is fine): For the signature check: As mentioned, it is a redundant check. The signature has already been checked at this point. This is even made obvious by the used types. The smart constructor is not perfect as discussed [here](https://github.com/paritytech/polkadot/issues/3455), but is still a reasonable security. For not importing to the dispute-coordinator: This should be good as the dispute coordinator does scrape backing votes from chain. This suffices in practice as a super majority of validators must have seen a backing fork in order for a candidate to get included and only included candidates pose a threat to our system. The import from chain is preferable over direct import of backing votes for two reasons: 1. The import is batched, greatly improving import performance. All backing votes for a candidate are imported with a single import. And indeed we were able to see in metrics that importing votes from chain is fast. 2. We do less work in general as not every candidate for which statements are gossiped might actually make it on a chain. The dispute coordinator as with the current implementation would still import and keep those votes around for six sessions. While redundancy is good for reliability in the event of bugs, this also comes at a non negligible cost. The dispute-coordinator right now is the subsystem with the highest load, despite the fact that it should not be doing much during mormal operation and it is only getting worse with more parachains as the load is a direct function of the number of statements. We'll see on Versi how much of a performance improvement this PR * Get rid of dead code. * Dont send approval vote * Make it pass CI * Bring back tests for fixing them later. * Explicit signature check. * Resurrect approval-voting tests (not fixed yet) * Send out approval votes in dispute-distribution. Use BTreeMap for ordered dispute votes. * Bring back an important warning. * Fix approval voting tests. * Don't send out dispute message on import + test + Some cleanup. * Guide changes. Note that the introduced complexity is actually redundant. * WIP: guide changes. * Finish guide changes about dispute-coordinator conceputally. Requires more proof read still. Also removed obsolete implementation details, where the code is better suited as the source of truth. * Finish guide changes for now. * Remove own approval vote import logic. * Implement logic for retrieving approval-votes into approval-voting and approval-distribution subsystems. * Update roadmap/implementers-guide/src/node/disputes/dispute-coordinator.md Co-authored-by: asynchronous rob <[email protected]> * Review feedback. In particular: Add note about disputes of non included candidates. * Incorporate Review Remarks * Get rid of superfluous space. * Tidy up import logic a bit. Logical vote import is now separated, making the code more readable and maintainable. Also: Accept import if there is at least one invalid signer that has not exceeded its spam slots, instead of requiring all of them to not exceed their limits. This is more correct and a preparation for vote batching. * We don't need/have empty imports. * Fix tests and bugs. * Remove error prone redundancy. * Import approval votes on dispute initiated/concluded. * Add test for approval vote import. * Make guide checker happy (hopefully) * Another sanity check + better logs. * Reasoning about boundedness. * Use `CandidateIndex` as opposed to `CoreIndex`. * Remove redundant import. * Review remarks. * Add metric for calls to request signatures * More review remarks. * Add metric on imported approval votes. * Include candidate hash in logs. * More trace log * Break cycle. * Add some tracing. * Cleanup allowed messages. * fmt * Tracing + timeout for get inherent data. * Better error. * Break cycle in all places. * Clarified comment some more. * Typo. * Break cycle approval-distribution - approval-voting. Co-authored-by: asynchronous rob <[email protected]>
-
- Aug 15, 2022
-
-
Muharem Ismailov authored
-
Alexander Samusev authored
* [ci] test-linux-stable and cancel-pipelines improvements * fail check-try-runtime * import changes from master * fix needs * fix check-try-runtime * remove cancel pipeline from check-try-runtime * return before_script to check-try-runtime
-
dependabot[bot] authored
Bumps [wasmtime](https://github.com/bytecodealliance/wasmtime) from 0.38.1 to 0.38.3. - [Release notes](https://github.com/bytecodealliance/wasmtime/releases) - [Changelog](https://github.com/bytecodealliance/wasmtime/blob/main/docs/WASI-some-possible-changes.md) - [Commits](https://github.com/bytecodealliance/wasmtime/compare/v0.38.1...v0.38.3) --- updated-dependencies: - dependency-name: wasmtime dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
- Aug 14, 2022
-
-
Sudip Ghimire authored
* Incorporate changes in kusama runtime * Incorporate changes in polkdot runtime * cargo update -p sp-io Co-authored-by: Shawn Tabrizi <[email protected]>
-
Kian Paimani authored
* Add nomination poools to Polkadot runtime * fmt + spellcheck * cargo run --quiet --profile=production --features runtime-benchmarks -- benchmark pallet --chain=polkadot-dev --steps=50 --repeat=20 --pallet=pallet_nomination_pools --extrinsic=* --execution=wasm --wasm-execution=compiled --header=./file_header.txt --output=./runtime/polkadot/src/weights/ * fiux * ".git/.scripts/bench-bot.sh" runtime polkadot-dev pallet_nomination_pools * ".git/.scripts/fmt.sh" 1 * Update runtime/polkadot/src/lib.rs Co-authored-by: Oliver Tale-Yazdi <[email protected]> * fix * fmt * Update runtime/polkadot/src/lib.rs Co-authored-by: Parity Bot <[email protected]> Co-authored-by: command-bot <> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
-
- Aug 12, 2022
-
-
Dmitry Markin authored
-
- Aug 11, 2022
-
-
Alexander Samusev authored
* [ci] Run check-runtime only for PRs * fix refs * remove pr ref from check-runtime * adjust dependent jobs * fix dependency
-
dependabot[bot] authored
Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.18.2 to 1.19.2. - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](https://github.com/tokio-rs/tokio/compare/tokio-1.18.2...tokio-1.19.2) --- updated-dependencies: - dependency-name: tokio dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
Andrei Sandu authored
* 1/3 validators suggest garbage candidates, but paras should make progress Signed-off-by: Andrei Sandu <[email protected]> * scale down test a bit Signed-off-by: Andrei Sandu <[email protected]> * Use docker paths and more paras Signed-off-by: Andrei Sandu <[email protected]> * dispute finality lag < 2 * scale down Signed-off-by: Andrei Sandu <[email protected]> * scale down more Signed-off-by: Andrei Sandu <[email protected]> * attempt fix Signed-off-by: Andrei Sandu <[email protected]> * one malus node Signed-off-by: Andrei Sandu <[email protected]> * Update zombienet_tests/functional/0003-parachains-garbage-candidate.toml Co-authored-by: Andronik <[email protected]> * Update zombienet_tests/functional/0003-parachains-garbage-candidate.toml Co-authored-by: Andronik <[email protected]> Signed-off-by: Andrei Sandu <[email protected]> Co-authored-by: Andronik <[email protected]>
-
Kian Paimani authored
* add unit tests to run runtime migrations * Update runtime/westend/src/lib.rs Co-authored-by: Mara Robin B. <[email protected]> * fix * fmt * Update runtime/westend/src/lib.rs Co-authored-by: Mara Robin B. <[email protected]>
-
- Aug 09, 2022
-
-
Nazar Mokrynskyi authored
* Trivial networking changes for Substrate PR https://github.com/paritytech/substrate/pull/11940 * update lockfile for {"substrate"} Co-authored-by: parity-processbot <>
-
- Aug 08, 2022
-
-
Nikos Kontakis authored
* Renaming CLI prunning and keep-blocks flags * update lockfile for {"substrate"} Co-authored-by: parity-processbot <>
-
- Aug 05, 2022
-
-
Bastian Köcher authored
-
Dmitry Markin authored
* Update RequestResponseConfig interface * minor: Bump CI * update lockfile for {"substrate"} * update lockfile for {"substrate"} Co-authored-by: parity-processbot <>
-
- Aug 04, 2022
-
-
Javier Viola authored
* rollback global version and use new version for beefy test * move zombienet to v1.2.51 * use global version in all tests * add image value to tests
-
ZhiYong authored
* Companion for substrate#11962 * update lockfile Co-authored-by: acatangiu <[email protected]>
-
Adrian Catangiu authored
Signed-off-by: acatangiu <[email protected]>
-
- Aug 03, 2022
-
-
Oliver Tale-Yazdi authored
The benchmarks have been run internally with at least two values even when called with --steps=1. substrate/#11890 changed this to explicitly require at least --steps=2. Signed-off-by: Oliver Tale-Yazdi <[email protected]>
-
Alexandru Vasile authored
* Bump jsonrpsee to v0.15.1 Signed-off-by: Alexandru Vasile <[email protected]> * Update cargo.lock Signed-off-by: Alexandru Vasile <[email protected]> * Minimal update to Cargo.lock Signed-off-by: Alexandru Vasile <[email protected]> * update substrate * update lockfile for {"substrate"} * update substrate master * Allow benchmark checks to fail Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: Niklas Adolfsson <[email protected]> Co-authored-by: parity-processbot <> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
-
- Aug 01, 2022
-
-
dependabot[bot] authored
Bumps [tracing](https://github.com/tokio-rs/tracing) from 0.1.34 to 0.1.35. - [Release notes](https://github.com/tokio-rs/tracing/releases) - [Commits](https://github.com/tokio-rs/tracing/compare/tracing-0.1.34...tracing-0.1.35) --- updated-dependencies: - dependency-name: tracing 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>
-
Oliver Tale-Yazdi authored
* Remove 'remove_member_wrong_refund' from phragmen weights Signed-off-by: Oliver Tale-Yazdi <[email protected]> * update lockfile for {"substrate"} Co-authored-by: parity-processbot <>
-
Alexander Samusev authored
-
Mara Broda authored
* westend: update weights * kusama: update weights * polkadot: update weights * rococo: update weights * update BlockExecutionWeight * kusama: readd phragmen remove_member_wrong_refund weight * polkadot: readd phragmen remove_member_wrong_refund weight
-
Shawn Tabrizi authored
* saturating xcm * Even more saturating Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
-
Mara Broda authored
-
- Jul 29, 2022
-
-
Adrian Catangiu authored
* node/service: add BEEFY to block import BEEFY block import implementation is basically noop for runtimes with dummy `BeefyApi`, therefore we can safely add it to all chains. * update lockfile for {"substrate"} Co-authored-by: parity-processbot <>
-
Xavier Lau authored
-
Koute authored
* Bump `parity-scale-codec` to 3.1.5 * Align tests to changes in substrate * Apply rustfmt * update lockfile for {"substrate"} Co-authored-by: parity-processbot <>
-
- Jul 28, 2022
-
-
Xavier Lau authored
* Remove Useless Inherent Data Provider * Remove Unused Deps
-
Mara Broda authored
* polkadot: update weights * kusama: update weights * westend: update weights * rococo: update weights * Reduce testing constants (#5787) Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: Oliver Tale-Yazdi <[email protected]>
-
Chevdor authored
* bump transcation_version * revert back transaction version for kusama and plokadot as they were bumped in the previous release Co-authored-by: Egor_P <[email protected]>
-
Chevdor authored
* Bump crate versions * Update cargo.lock
-
Chevdor authored
-