Skip to content
  1. Dec 25, 2021
  3. 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
  5. Dec 23, 2021
  7. Dec 22, 2021
  9. Dec 21, 2021
  11. Dec 20, 2021
  13. Dec 18, 2021
  15. Dec 17, 2021
  17. Dec 16, 2021
  19. Dec 15, 2021
  21. Dec 14, 2021
    • Sergey Pepyakin's avatar
      PVF validation host: do not alter niceness (#4525) · 1493fed1
      Sergey Pepyakin authored 
      We wanted to change niceness to accomodate the fact that some of the
preparation tasks are low priority. For example, when a node sees that
there is a new para was onboarded the node may start preparing right
away. Since all other activities are more important, such as network I/O
or validation of the backed candidates and preparation of the
immediatelly needed PVFs.

However, it turned out that this approach does not work: generally
non-root processes can only decrease niceness and they cannot increase
it to the previous value, as was assumed by the code.

Apart from that, https://github.com/paritytech/polkadot/pull/4123
assumes all PVFs are prepared in the same way. Specifically, that if a
PVF preparation failed before, then PVF pre-checking will also report
that it was failed, even though it could happen that preparation failed
due to being low-priority. In order to avoid such cases, we decided to
simplify the whole preparation model. Preparation under low priority
does not work well with that.

Closes https://github.com/paritytech/polkadot/issues/4520
      1493fed1
    • Sergey Pepyakin's avatar
      pvf-precheck: teach runtime-api to work with versions (#4510) · 2ccbf38b
      Sergey Pepyakin authored 
      As part of #3211 we will need to add a couple of runtime APIs. That
change is coming in a following PR.

The runtime API for pre-checking will be introduced with a version bump
for `ParachainHost`. This commit prepares the ground for that change,
by introducing a error condition that signals that the given API is not
supported.
      2ccbf38b
    • Koute's avatar
      Companion for Substrate#10394 (#4471) · c328d1e6
      Koute authored 
      * Align PVF executor to changes in Substrate

* Update to the newest `substrate`
      c328d1e6
    • Gavin Wood's avatar
      Companion #10403: Remove Default for AccountId (#4500) · ca72ad63
      Gavin Wood authored 
      * Some work

* Fixes

* Tests builds

* Fixes

* Fixes

* Fixes

* Fixes

* Fixes

* Formatting

* Formatting

* Fix

* Fixes

* Fixes

* Fixes

* Fixes

* Update Cargo.lock

* Bump

* Fixes
      ca72ad63
  23. Dec 13, 2021
  25. Dec 12, 2021