Skip to content
  1. Dec 21, 2021
    • Adrian Catangiu's avatar
      Companion for Substrate#10445 (#4506) · 30423f79
      Adrian Catangiu authored
      * runtimes: use updated BeefyApi
      
      * update lockfile for substrate
      30423f79
    • Sergey Pepyakin's avatar
      pvf-precheck: update rustdoc for paras module (#4459) · 0e046a00
      Sergey Pepyakin authored
      Basically updates the docs for the paras module.
      0e046a00
    • Sergey Pepyakin's avatar
      pvf-precheck: hook up runtime API (#4542) · 3cb138d2
      Sergey Pepyakin authored
      
      
      This commit hooks up the API provided by #4457 to the runtime API
      subsystem. In a following PR this API will be consumed by the PVF
      pre-checking subsystem.
      
      Co-authored-by: default avatarChris Sosnin <[email protected]>
      
      Co-authored-by: default avatarChris Sosnin <[email protected]>
      3cb138d2
    • Sergey Pepyakin's avatar
      parachains: Fix configuration module (#4540) · 5a3ee43c
      Sergey Pepyakin authored
      
      
      * parachains: Fix configuration module
      
      Closes #4529
      Closes #4533
      
      I figured that trying to avoid updates does not really worth it to keep.
      This is because we seem to not update the configuration often and when
      we do we approach this carefully. Thus possibility of a redundant update
      is really negligable. At the same time, if such a redundant update does
      happen then the effects of that are really small: just some wasted
      storage interactions.
      
      On the other hand, making it work was a little bit annoying. With the
      proper fix for the pending updates this would be even more annoying
      since now we would have to add combinatorically more cases to test this.
      
      So I figured that I will just scrap that and simplify the code.
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=kusama-dev --steps=50 --repeat=20 --pallet=runtime_parachains::configuration --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/kusama/src/weights/runtime_parachains_configuration.rs
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=polkadot-dev --steps=50 --repeat=20 --pallet=runtime_parachains::configuration --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/polkadot/src/weights/runtime_parachains_configuration.rs
      
      * cargo run --quiet --release --features=runtime-benchmarks -- benchmark --chain=westend-dev --steps=50 --repeat=20 --pallet=runtime_parachains::configuration --extrinsic=* --execution=wasm --wasm-execution=compiled --heap-pages=4096 --header=./file_header.txt --output=./runtime/westend/src/weights/runtime_parachains_configuration.rs
      
      * review fixes
      
      Co-authored-by: default avatarParity Bot <[email protected]>
      5a3ee43c
    • dependabot[bot]'s avatar
      Bump bounded-vec from 0.4.0 to 0.5.0 (#4082) · 478ac958
      dependabot[bot] authored
      
      
      Bumps [bounded-vec](https://github.com/ergoplatform/bounded-vec) from 0.4.0 to 0.5.0.
      - [Release notes](https://github.com/ergoplatform/bounded-vec/releases)
      - [Changelog](https://github.com/ergoplatform/bounded-vec/blob/develop/CHANGELOG.md)
      - [Commits](https://github.com/ergoplatform/bounded-vec/compare/v0.4.0...v0.5.0)
      
      ---
      updated-dependencies:
      - dependency-name: bounded-vec
        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>
      478ac958
  2. Dec 20, 2021
  3. Dec 18, 2021
  4. Dec 17, 2021
  5. Dec 16, 2021
  6. Dec 15, 2021
  7. 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