- Apr 14, 2022
-
-
stanly-johnson authored
* remove no_op event * ensure no transferred event emitted Co-authored-by: Oliver Tale-Yazdi <[email protected]>
-
Ross Bulat authored
* commission-changed-event-and-deposit * deposit_event fix * commission_changed_event_works * fmt * CommissionChanged -> ValidatorPrefsUpdated * event ValidatorPrefs * updated commet * fmt * Update frame/staking/src/pallet/mod.rs Co-authored-by: joe petrowski <[email protected]> * Update frame/staking/src/pallet/mod.rs Co-authored-by: joe petrowski <[email protected]> * Update frame/staking/src/tests.rs Co-authored-by: joe petrowski <[email protected]> Co-authored-by: joe petrowski <[email protected]>
-
Nazar Mokrynskyi authored
* Update wasmtime to 0.35.2 and default `zstd` features in all crates * Update wasmtime to 0.35.3
-
Liu-Cheng Xu authored
Othewise the compiler will complain if someone passes something that implements `CliConfiguration<DVC>` but `DVC` is not the default `()`.
-
- Apr 13, 2022
-
-
Bastian Köcher authored
It can happen that `+ 1` overflows `p.signature[1]` ;D (I have seen this in the CI).
-
Bastian Köcher authored
* Document the chain spec format * Update client/chain-spec/src/lib.rs Co-authored-by: Pierre Krieger <[email protected]> * Update client/chain-spec/src/lib.rs Co-authored-by: Pierre Krieger <[email protected]> * Apply suggestions from code review Co-authored-by: Sacha Lansky <[email protected]> * Update client/chain-spec/src/lib.rs Co-authored-by: André Silva <[email protected]> * Update client/chain-spec/src/lib.rs Co-authored-by: André Silva <[email protected]> * Mention extensions Co-authored-by: Pierre Krieger <[email protected]> Co-authored-by: Sacha Lansky <[email protected]> Co-authored-by: André Silva <[email protected]>
-
Alexander Samusev authored
-
Oliver Tale-Yazdi authored
* Box events Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Fix tests Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Revert "Box events" This reverts commit 9fb1887cd23eb272844d63640b0b2d9ba3e549a1. * Revert "Fix tests" This reverts commit 981c50f23a7c514c9527299734bc6bc5b77a817f. * Use simpler approach Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Update doc Signed-off-by: Oliver Tale-Yazdi <[email protected]>
-
Adrian Catangiu authored
* beefy-gadget: allow custom runtime api provider * beefy-gadget: use mock runtime api in tests * pallet-mmr: expose mmr root from state through runtime API * beefy-gadget: get mmr root from runtime state * pallet-beefy-mmr: remove MmrRoot from header digests * frame/mmr: move mmr primitives out of frame * frame/mmr: completely move primitives out of frame * address review comments * beefy-mmr: bring back mmr root from header digest * clippy fixes for rustc 1.60 * address review comments
-
- Apr 12, 2022
-
-
Qinxuan Chen authored
Signed-off-by: koushiro <[email protected]>
-
Denis_P authored
-
Bastian Köcher authored
* Finality notification: Optimize calculation of stale heads While looking into some problem on Versi where a collator seemed to be stuck. I found out that it was not stuck but there was a huge gap between last finalized and best block. This lead to a lot leaves and it was basically trapped inside some loop of reading block headers from the db to find the stale heads. While looking into this I found out that `leaves` already supports the feature to give us the stale heads relative easily. However, the semantics change a little bit. Instead of returning all stale heads of blocks that are not reachable anymore after finalizing a block, we currently only return heads with a number lower than the finalized block. This should be no problem, because these other leaves that are stale will be returned later when a block gets finalized which number is bigger than the block number of these leaves. While doing that, I also changed `tree_route` of the `FinalityNotification` to include the `old_finalized`. Based on the comment I assumed that this was already part of it. However, if wanted, I can revert this change. * FMT * Update client/service/src/client/client.rs Co-authored-by: André Silva <[email protected]> * Do not include the last finalized block * Rename function * FMT * Fix tests * Update figure Co-authored-by: André Silva <[email protected]>
-
Xiliang Chen authored
* add has_identity * Update frame/identity/src/lib.rs Co-authored-by: Bastian Köcher <[email protected]> * update * update Co-authored-by: Bastian Köcher <[email protected]>
-
- Apr 11, 2022
-
-
Koute authored
* Add new hardware and software metrics * Move sysinfo tests into `mod tests` * Correct a typo in a comment * Remove unnecessary `nix` dependency * Fix the version tests * Add a `--disable-hardware-benchmarks` CLI argument * Disable hardware benchmarks in the integration tests * Remove unused import * Fix benchmarks compilation * Move code to a new `sc-sysinfo` crate * Correct `impl_version` comment * Move `--disable-hardware-benchmarks` to the chain-specific bin crate * Move printing out of hardware bench results to `sc-sysinfo` * Move hardware benchmarks to a separate messages; trigger them manually * Rename some of the fields in the `HwBench` struct * Revert changes to the telemetry crate; manually send hwbench messages * Move sysinfo logs into the sysinfo crate * Move the `TARGET_OS_*` constants into the sysinfo crate * Minor cleanups * Move the `HwBench` struct to the sysinfo crate * Derive `Clone` for `HwBench` * Fix broken telemetry connection notification stream * Prevent the telemetry connection notifiers from leaking if they're disconnected * Turn the telemetry notification failure log into a debug log * Rename `--disable-hardware-benchmarks` to `--no-hardware-benchmarks`
-
Bastian Köcher authored
* Prepare for rust stable 1.59 Besides preparing the UI tests this also adds a new script update-rust-stable.sh script for simplifying the update of a rust stable version. This script will run all UI tests for the new rust stable version and updating the expected output. * Ensure we run the UI tests in CI * use staging ci image * More test updates * Unignore test (#11097) * empty commit for pipeline rerun * empty commit for pipeline rerun * Try to make clippy happy * More clippy fixes * FMT * ci image production Co-authored-by: alvicsam <[email protected]> Co-authored-by: Alexander Samusev <[email protected]>
-
Dominique authored
* Updated docs for method 'set_payee' * Updated docs for method 'set_controller'
-
Xiliang Chen authored
-
Davide Galassi authored
* Convert cli options from 'CamelCase' to 'kebab-case' * Remove not required 'as_str' for 'ExecutionStrategy' option
-
- Apr 09, 2022
-
-
Davide Galassi authored
* Remove useless trait bound and `move` instructions * cargo fmt
-
- Apr 08, 2022
-
-
Sergejs Kostjucenko authored
* Add GHA for custom PR review * Change FILES rule settings * Update rules according to feedback * Update .github/pr-custom-review.yml Co-authored-by: Denis Pisarev <[email protected]> * CI: PRCR new
🔒 team is locks-review * CI: rename a confusing step * Update .github/workflows/pr-custom-review.yml Co-authored-by: João Paulo Silva de Souza <[email protected]> * CI: use a proper new team for as per discussion with @drahnr it was decided to create a dedicated team for reviewing runtime files * Update pr-custom-review.yml * Update .github/workflows/pr-custom-review.yml Co-authored-by: João Paulo Silva de Souza <[email protected]> * Update .github/workflows/pr-custom-review.yml Co-authored-by: João Paulo Silva de Souza <[email protected]> Co-authored-by: Denis Pisarev <[email protected]> Co-authored-by: TriplEight <[email protected]> Co-authored-by: Denis Pisarev <[email protected]> Co-authored-by: João Paulo Silva de Souza <[email protected]> -
Koute authored
* Catch panics on the FFI boundary between the runtime and the host for `wasmtime` * Use an already existing test runtime function * Merge the tests together
-
dependabot[bot] authored
Bumps [lru](https://github.com/jeromefroe/lru-rs) from 0.7.3 to 0.7.5. - [Release notes](https://github.com/jeromefroe/lru-rs/releases) - [Changelog](https://github.com/jeromefroe/lru-rs/blob/master/CHANGELOG.md) - [Commits](https://github.com/jeromefroe/lru-rs/compare/0.7.3...0.7.5) --- updated-dependencies: - dependency-name: lru 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>
-
dependabot[bot] authored
Bumps [impl-trait-for-tuples](https://github.com/bkchr/impl-trait-for-tuples) from 0.2.1 to 0.2.2. - [Release notes](https://github.com/bkchr/impl-trait-for-tuples/releases) - [Commits](https://github.com/bkchr/impl-trait-for-tuples/compare/v0.2.1...v0.2.2) --- updated-dependencies: - dependency-name: impl-trait-for-tuples 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>
-
João Paulo Silva de Souza authored
-
- Apr 07, 2022
-
-
Oliver Tale-Yazdi authored
* Restructure benchmark commands Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Add benchmark block test Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Fixup imports Signed-off-by: Oliver Tale-Yazdi <[email protected]> * CI Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Review fixes Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Extend error message Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Apply suggestions from code review Co-authored-by: Zeke Mostov <[email protected]> * Review fixes Signed-off-by: Oliver Tale-Yazdi <[email protected]> * Add commands to node-template Signed-off-by: Oliver Tale-Yazdi <[email protected]> Co-authored-by: Zeke Mostov <[email protected]>
-
João Paulo Silva de Souza authored
syntax in accordance to https://github.com/paritytech/pr-custom-review/tree/5814820aa0e5d35412f31dc02f9d130a8b138cae#configuration-syntax rules in accordance to https://github.com/paritytech/pr-custom-review/blob/da1d81b9fd39705cc8b37f59235283801c818708/rules.md
-
Bastian Köcher authored
These docs didn't mention how the removal works internally. This is important for the user to know that calling such a method multiple times in the same block leads always to the same result.
-
Stephen Shelton authored
* Apply WeightToFeePolynomials to length fee * Remove TransactionByteFee * Add test cases for ConstantModifierFee * Restore import * Use pallet::constant_name * Remove irrelevant TODO comment * Update frame/support/src/weights.rs * Update frame/transaction-payment/src/lib.rs * Update frame/transaction-payment/src/lib.rs * Update frame/transaction-payment/src/lib.rs Co-authored-by: Kian Paimani <[email protected]> * s/ConstantModifierFee/ConstantMultiplier/ * Impl LengthToFee for test configs * fmt * Remove unused import * Impl WeightToFeePolynomial for byte fee in ExtBuilder * Remove unused import * fix doc Co-authored-by: Bastian Köcher <[email protected]> Co-authored-by: Kian Paimani <[email protected]> Co-authored-by: Shawn Tabrizi <[email protected]>
-
Kian Paimani authored
* relax input conditions of fixed::checked_from_integer * Fix build
-
Niklas Adolfsson authored
* fix(bin/node): remove unsed dep jsonrpsee * chore(remote ext): update jsonrpsee v0.10.1 * chore(try runtime): update jsonrpsee v0.10.1 * Update utils/frame/try-runtime/cli/src/commands/follow_chain.rs * cargo fmt
-
- Apr 06, 2022
-
-
Alexander Samusev authored
* [ci] Remove vault * remove anchors
-
Davide Galassi authored
* Grandpa revert procedure * Trigger ci pipeline * Test rename * Update client/finality-grandpa/src/authorities.rs Co-authored-by: André Silva <[email protected]>
-
Davide Galassi authored
* Fix fork-tree descendent check * Add test assertions for the fix * Improve documentation * Nitpicks
-
Bastian Köcher authored
This pr changes all default execution strategies to `Wasm`. This is basically a deprecation of the native runtime. While the native runtime isn't removed and can still be used, it will not be used anymore by default. This will also improve the usage for people who want to run random commits, which most often forget to run with `--execution wasm`. Otherwise they often run into storage root mismatches because of using the native runtime.
-
- Apr 05, 2022
-
-
dependabot[bot] authored
* Bump enumflags2 from 0.6.4 to 0.7.4 Bumps [enumflags2](https://github.com/NieDzejkob/enumflags2) from 0.6.4 to 0.7.4. - [Release notes](https://github.com/NieDzejkob/enumflags2/releases) - [Commits](https://github.com/NieDzejkob/enumflags2/compare/v0.6.4...v0.7.4) --- updated-dependencies: - dependency-name: enumflags2 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> * use `#[bitflags]` attribute macro Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Shawn Tabrizi <[email protected]>
-
Alexander Theißen authored
-
Zhenghao Lu authored
-
- Apr 04, 2022
-
-
Bastian Köcher authored
* transactional: Fix some nitpicks This fixes some nitpicks related to the transactional storage stuff from me. As everything was merged too fast, here are some nitpicks from me. First, the entire functionality is moved into its own file to have a clear separation. Secondly I changed the `set_transactional_level` to not take `Layer` by reference. Besides that I have added some docs etc. * Add some comment * Move tests *
🤦 -
Davide Galassi authored
-
Alexander Theißen authored
This reverts commit a69b8eb4a28f365a4a4b2fc295a693ec4d3d3cd5.
-