1. Nov 30, 2021
    • dependabot[bot]'s avatar
      Bump clap from 2.33.3 to 2.34.0 (#4414) · 0cca1d04
      dependabot[bot] authored
      Bumps [clap](https://github.com/clap-rs/clap) from 2.33.3 to 2.34.0.
      - [Release notes](https://github.com/clap-rs/clap/releases)
      - [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md)
      - [Commits](https://github.com/clap-rs/clap/commits
      
      )
      
      ---
      updated-dependencies:
      - dependency-name: clap
        dependency-type: direct:production
        update-type: version-update:semver-minor
      ...
      
      Signed-off-by: default avatardependabot[bot] <[email protected]>
      
      Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
      0cca1d04
    • Robert Klotzner's avatar
      Double time we give spawned tasks. (#4415) · ce27250c
      Robert Klotzner authored
      * Double time we give spawned tasks.
      
      * Increase time even more, for better robustness.
      ce27250c
    • zjb0807's avatar
      Companion for #10324 - update frame-benchmarking/runtime-benchmarks (#4387) · a7843702
      zjb0807 authored
      
      
      * update frame-benchmarking/runtime-benchmarks
      
      * Update Substrate
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      a7843702
    • Lldenaurois's avatar
      Revert "remove provisioner checks (#4254)" (#4375) · 22431214
      Lldenaurois authored
      * Revert "remove provisioner checks (#4254)"
      
      This reverts commit d5d916a9.
      
      * Remove TODO in implementer's guide
      22431214
    • Chevdor's avatar
    • Sergey Pepyakin's avatar
      pvf-precheck: Add `PvfCheckStatement` to polkadot-primitives (#4406) · 5e5aa668
      Sergey Pepyakin authored
      * pvf-precheck: Add `sign` in subsystem-util
      
      Right now, most of operations that sign stuff in polkadot protocol are
      handled by a very convenient tool - `Signed`. However `Signed` assumes
      that whatever is signed is anchored to some `parent_hash` which works
      for most cases, but does not work for others.
      
      One instance of such a case is pre-checking (#3211). There validators
      submit signed votes on-chain. A vote is valid for the entire session. If
      we were to use `Signed` we would have to root a vote in some block of
      that session and during vote verification check that this block is
      indeed within the session. This is especially annoying since we agreed
      to use unsigned extrinsics to submit votes and we need to make the
      unsigned extrinsic validation as slim as possible.
      
      (FWIW, the definition of a pre-checking vote can be seen in the next
      diff in the stack)
      
      That's the reason why we opted-out from using `Signed` for pre-checking
      and decided to go with the manual signing approach. Almost every piece
      of machinery is in place except for signing which is presented in this
      PR.
      
      * pvf-precheck: Add `PvfCheckStatement` to polkadot-primitives
      
      This is an insubstantial PR that just unlocks PRs down the line. This PR
      is a part of #3211.
      
      Regarding the `PvfCheckStatement` struct itself: this is a structure
      that will be used to convert from/into the binary representation and
      ultimately will be used to sign and submit votes onto chain.
      5e5aa668
    • Sergey Pepyakin's avatar
      pvf-precheck: Add `sign` in subsystem-util (#4407) · 9f778ccf
      Sergey Pepyakin authored
      Right now, most of operations that sign stuff in polkadot protocol are
      handled by a very convenient tool - `Signed`. However `Signed` assumes
      that whatever is signed is anchored to some `parent_hash` which works
      for most cases, but does not work for others.
      
      One instance of such a case is pre-checking (#3211). There validators
      submit signed votes on-chain. A vote is valid for the entire session. If
      we were to use `Signed` we would have to root a vote in some block of
      that session and during vote verification check that this block is
      indeed within the session. This is especially annoying since we agreed
      to use unsigned extrinsics to submit votes and we need to make the
      unsigned extrinsic validation as slim as possible.
      
      (FWIW, the definition of a pre-checking vote can be seen in the next
      diff in the stack)
      
      That's the reason why we opted-out from using `Signed` for pre-checking
      and decided to go with the manual signing approach. Almost every piece
      of machinery is in place except for signing which is presented in this
      PR.
      9f778ccf
    • Bernhard Schuster's avatar
      make chain selection typed and more explicit in naming and logging (#4345) · 13f0e5d7
      Bernhard Schuster authored
      * minor: assure conditions match
      
      This simplifies visual integrity checks that an overseer is connected
      when it has to be.
      
      * fix: avoid printing a misleading log in case of the disabled disputes feature
      
      * chore: comments
      
      * add expressive types for the selection algorithm
      13f0e5d7
  2. Nov 29, 2021
  3. Nov 28, 2021
  4. Nov 27, 2021
  5. Nov 26, 2021
    • Sergey Pepyakin's avatar
      Do not log PVF prunning every hour (#4372) · f6b42151
      Sergey Pepyakin authored
      This lowers the level of the PVF pruning.
      
      Closes https://github.com/paritytech/polkadot/issues/4361
      f6b42151
    • Sergey Pepyakin's avatar
      Impose new restrictions on paras init and cleanup (#4360) · bce0e5ac
      Sergey Pepyakin authored
      * Impose new restrictions on paras init and cleanup
      
      For upcoming PVF pre-checking feature we will need to impose a couple of
      new restrictions for:
      
      - `schedule_para_initialize`.
      - `schedule_para_cleanup`.
      
      Specifically, for the former we do not want to allow registration of
      wasm blob that is empty, i.e. 0 bytes. While that currently already
      does not make a lot of sense, it allows us to simplify the PVF
      pre-checking logic: if this PR is deployed before the following changes
      for PVF prechecking then we can be sure that no paras onboarding have to
      have to go through the PVF pre-checking. In case, we deploy it
      altogether this property will allow us to distingush paras that came in
      before PVF pre-checking.
      
      For `schedule_para_cleanup` we do not want to allow offboarding of paras
      that are undergoing the upgrade process. While this is not a harsh
      restriction this change allows us to avoid making the PVF prechecking
      more complicated than it has to be.
      
      * Add a test for schedule_para_initialize
      
      * Link to `ParaLifecycle::is_stable` in docs.
      
      * `schedule_para_{init,cleanup}` docs
      
      Now they link to their original declarations in the pallet for more
      details.
      bce0e5ac
    • sandreim's avatar
      Fix Provisioner dispute metrics naming (#4374) · e4e22f40
      sandreim authored
      
      
      * update dispute metric names
      
      Signed-off-by: default avatarAndrei Sandu <[email protected]>
      
      * update
      
      Signed-off-by: default avatarAndrei Sandu <[email protected]>
      e4e22f40
    • Keith Yeung's avatar
      Update W3F URL links (#4376) · bbde75e8
      Keith Yeung authored
      bbde75e8
  6. Nov 25, 2021
  7. Nov 24, 2021
  8. Nov 23, 2021
    • Zeke Mostov's avatar
      Inherent filtering follow up (#4305) · 90e12734
      Zeke Mostov authored
      
      
      * Add feature more feature gating for benchmarking + tests
      
      * New line
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=kusama-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras_inherent --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/kusama/src/weights/runtime_parachains_paras_inherent.rs
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=polkadot-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras_inherent --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/polkadot/src/weights/runtime_parachains_paras_inherent.rs
      
      * Do not assume we use max validators per core
      
      * Use kusama weights for rococo (hopefully temp)
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras_inherent --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/runtime_parachains_paras_inherent.rs
      
      * Add more validity votes when neccesary
      
      * Some fixes for the last commit
      
      * Restore westend weights
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras_inherent --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/runtime_parachains_paras_inherent.rs
      
      * Revert bad westend weights write
      
      * Make sure to update val idx before skipping
      
      * Fix validity vote range to max at group size'
      
      * Temp setup for rococo
      
      * cargo run --quiet --release --features runtime-benchmarks -- benchmark --chain=rococo-dev --steps=50 --repeat=20 --pallet=runtime_parachains::paras_inherent --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --output=./runtime/rococo/src/weights/runtime_parachains_paras_inherent.rs --header=./file_header.txt
      
      * Augment generated Rococo weights
      
      * Make it compile
      
      * Revert range for enter_backed_candidates_variable
      
      * Delete runtime/kusama/src/weights/runtime_paras_paras_inherent.rs
      
      Co-authored-by: default avatarParity Bot <[email protected]>
      90e12734
  9. Nov 22, 2021
  10. Nov 20, 2021
    • Javier Viola's avatar
      introduce malus + zombienet based integration tests (#4131) · ea5dbd04
      Javier Viola authored
      
      
      * test/malus: craft the first maliciously disputing actor
      
      * initial draft
      
      * Add Dockerfile and instructions how to use it to build malus image locally
      
      * Forgot one flag for the build cmd
      
      * we are not docker specific, we are happy to use any containerruntime
      
      * shuffle things around
      
      * add initial tera based integration test
      
      * chores
      
      * fixins
      
      * simple setup to start
      
      * other samples (WIP)
      
      * add Docker version with cargo-chef
      
      * update substarte and small change of orders in commands in the container file
      
      * metrics one
      
      * fmt
      
      * minor
      
      * fixin
      
      * fix metric names
      
      * -d
      
      * add open gauge
      
      * fmt
      
      * spellcheck
      
      * fix test
      
      * adjust to changed error messages
      
      * refactor, more malus impls
      
      * more malus changes
      
      * foo
      
      * minor cleanup
      
      * suggest garbage candidate
      
      * chore
      
      * fix suggest garabge malus
      
      * malus: back garbage candidate
      
      * cargo lock
      
      * re-introduce metrics
      
      * chore: cargo fmt
      
      * undoe 1.54.0 output, CI uses 1.53.0 rustc
      
      * update location of js types
      
      * Fix trybuild
      
      * add tag to image name also; this will be replaced in the prod version
      
      * Tests fixed
      
      * add some fix me
      
      * add dockerfile for ci
      
      * Add docker file for malus for ci
      
      * use variables in .toml file
      
      * add chnages for malus test
      
      * some fixes
      
      * some more fixes
      
      * Update .gitlab-ci.yml
      
      * add local build for polkadot and malus
      
      * some fixes
      
      * enable disputes feature in CI
      
      * ok, ok
      
      * rename: MsgFilter -> MessageInterceptor
      
      * remove TODO that would not have worked
      
      * intercept
      
      * refactor
      
      * fix README and containers
      
      * fix
      
      * chore: cargo fmt
      
      * avoid some more malus-$VARIANT references
      
      * fix argument order
      
      * chore: add about
      
      * Update sanity check in relay chain selection
      
      * fix order, add dispute-unavailable-block malus
      
      * fixup: avoid underflow issue
      
      * it's all u32
      
      * fix conditional use
      
      * Revert "it's all u32"
      
      This reverts commit 6b3ae25bfd0bbf0b51d90d743642a75a4a815d6e.
      
      * Revert "fixup: avoid underflow issue"
      
      This reverts commit 336cbe2938e9720f870d37d8feeab7ca69200f47.
      
      * Revert "Update sanity check in relay chain selection"
      
      This reverts commit 970647f35e1116136e12fd91cd9f2fb7e18ad28d.
      
      * update the malus bin
      
      * Update node/malus/integrationtests/0003-dispute-unavailable-block.feature
      
      Co-authored-by: default avatarAndronik Ordian <[email protected]>
      
      * add some FIXME reminders
      
      * update path to index.js
      
      * Update .gitlab-ci.yml
      
      * Update node/malus/integrationtests/0001-dispute-valid-block.toml
      
      * try 1: make malus test run
      
      * chore: cargo fmt
      
      * temporary fix
      
      * use subcommand syntax from latest gurke
      
      * cargo +nightly fmt
      
      * add collator to a a test
      
      * docs: add env vars to README
      
      * update ci to run dispute-valid-block test
      
      * needs the polkadot image
      
      * Fix path for nodejs container
      
      * post merge fix
      
      * download proper dir  containg configs for malus test
      
      * update the malus ci job
      
      * rm a whitespace
      
      * temp build for malus
      
      * use correct build command for temp malus
      
      * remove subcommands for now
      
      * set max validators per core in the default HostConfig
      
      * tabs
      
      * update beefy
      
      * fixup
      
      * fixup II
      
      * make one variant compile
      
      * make other variants compile
      
      * revert changes to chain_spec
      
      * fmt
      
      * build malus image from polkadot-test-malus again
      
      * revert unrelated changes
      
      * try fixing build-malus job
      
      * Revert "remove subcommands for now"
      
      This reverts commit 5d8292bc49252124937affec4b7c28181a5deb7e.
      
      * try fixing build-malus job II
      
      * MVP working dispute-ancestor
      
      * renames
      
      * fix PVF execution on malus
      
      * fix test
      
      * fix typo
      
      * fmt
      
      * checkmate
      
      * try something
      
      * make it actually work
      
      * some tweaks to 01 feature test
      
      * fmt
      
      * sleep a bit more
      
      * complete wococoization
      
      * some tweaks to 01 feature test
      
      * typo fix
      
      * use correct metric names
      
      * fix
      
      * ffs
      
      * .
      
      * try some rearrangement
      
      * Attempt to wait till initial node bootstrap in test
      
      * Fix test syntax
      
      * Run malus tests with v2 script
      
      * Proper symlink created
      
      * simnet v14
      
      * add zombienet tests
      
      * add zombie net test - draft
      
      * add more tests to dispute suite
      
      * add within to fix tests
      
      * replace test directory and start test migration
      
      * migrate all the tests
      
      * add timeout to tests
      
      * reduce debug
      
      * make easy to test in dev
      
      * set appropriated debug
      
      * use image from ci
      
      * fix config for test
      
      * set images from ci
      
      * fix config
      
      * add COLIMAGE env
      
      * tweek tests
      
      * reduce debug
      
      * typo
      
      * wip, migrate old test to zombie-net
      
      * adjunt test config for zombie-net
      
      * run mauls 0001 test only
      
      * clean and setup smoke-test in zombie-net
      
      * add extra time to assertinons
      
      * clean code to merge and improve README
      
      * add info to access logs
      
      * improved readme
      
      * merge master and resolve conflicts
      
      * Update zombienet_tests/README.md
      
      Co-authored-by: default avatarBernhard Schuster <[email protected]>
      
      * clean and consolidate zombienet name
      
      * change runner in gitlab
      
      * add comment explain why we use wococo
      
      * change tag for runner
      
      * remove unused tests
      
      * remove dup Dockerfile and update description
      
      * fmt
      
      * fix compilation post-merge
      
      * fmt
      
      * cut me Some slack
      
      Co-authored-by: default avatarBernhard Schuster <[email protected]>
      Co-authored-by: default avatarradupopa2010 <[email protected]>
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      Co-authored-by: default avatarAnton Gavrilov <[email protected]>
      Co-authored-by: default avatarAndronik Ordian <[email protected]>
      Co-authored-by: default avatarLldenaurois <[email protected]>
      ea5dbd04
    • Lldenaurois's avatar
      Replicate Rob's PR (#4337) · e35ebee0
      Lldenaurois authored
      e35ebee0
  11. Nov 19, 2021