Skip to content
  1. Jan 04, 2022
  3. Jan 03, 2022
    • Martin Pugh's avatar
      Update RELEASE.md to reflect reality (#4570) · 2f7b042c
      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.
      2f7b042c
    • Keith Yeung's avatar
      Set CurrentCodeHash before running some dispatchable benchmarks (#4645) · 5047ef8e
      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: default avatarParity Bot <[email protected]>
      5047ef8e
    • Sergey Pepyakin's avatar
      paras: split tests (#4636) · 575775a1
      Sergey Pepyakin authored 
      This is only a module structure change: the tests module was promoted to
have its own file.
      575775a1
  5. Jan 02, 2022
  7. Jan 01, 2022
  9. Dec 31, 2021
  11. Dec 30, 2021
  13. Dec 29, 2021
  15. Dec 28, 2021
  17. Dec 27, 2021
    • sandreim's avatar
      Bump sleep from 10 to 30s (#4613) · 979fa1f5
      sandreim authored 
      

Signed-off-by: default avatarAndrei Sandu <[email protected]>
      979fa1f5
    • Sergey Pepyakin's avatar
      configuration: Unified consistency checks (#4581) · 4d768787
      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.
      4d768787
    • ordian's avatar
      zombienet: fixed adder-collator image for the smoke test (#4600) · d077ac2c
      ordian authored 
      

* zombinet: fixed adder-collator image for the smoke test

* update COL_IMAGE

* bump zombienet version

* try a different version

Co-authored-by: default avatarJavier Viola <[email protected]>
      d077ac2c
    • João Paulo Silva de Souza's avatar
      make check-dependent-* only be executed in PRs (#4588) · b3e36538
      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.
      b3e36538
    • ordian's avatar
      session_info: add dispute_period and random_seed (#4547) · 9efb223a
      ordian authored
      9efb223a
    • ordian's avatar
      session-info: add new fields + migration (#4545) · b342ae11
      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: default avatarJavier Viola <[email protected]>
      b342ae11
  19. Dec 25, 2021
  21. Dec 24, 2021
    • cheme's avatar
      Companion for substrate#9732 (#4104) · 48dc6750
      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 <>
      48dc6750
    • Robert Klotzner's avatar
      Better logs and metrics on PoV fetching. (#4593) · 03495958
      Robert Klotzner authored
      03495958
  23. Dec 23, 2021
  25. Dec 22, 2021