Skip to content
  1. Apr 26, 2022
  3. Apr 25, 2022
    • tgmichel's avatar
      Add `chain-info` Subcommand (#11250) · 5eb2e329
      tgmichel authored 
      

* Add `blockchain-info` Subcommand

* Update comment

* Cleanup

* Cleanup

* Use `sync_run`

* Use `sc_client_db` utility fns instead service backend

* Use service `Backend` builder

* Impl `From<sp_blockchain::Info>`

* Rename to `chain-info`

* fmt

* Copyright year

Co-authored-by: default avatarBastian Köcher <[email protected]>

* Expose `DatabaseParams`

Co-authored-by: default avatarBastian Köcher <[email protected]>
      5eb2e329
    • Bastian Köcher's avatar
      pallet-asset: Fix transfer of a large amount of an asset (#11241) · 2541efdb
      Bastian Köcher authored 
      

* pallet-asset: Fix transfer of a large amount of an asset

Before this pr transferring a large amount of an asset would check that transferring the asset would
not overflow the supply of the asset. However, it doesn't make sense to check for asset supply
overflow when we just transfer from one account to another account and don't increase the supply in
any way. It also required to extend the `can_deposit` method of `fungible` and `fungibles` with a
`mint` parameter. If this parameter is set to `true`, it means we want to mint the amount of an
asset before transferring it into an account. For `can_withdraw` we don't need to add an extra
parameter, because withdrawing should never be able to underflow the supply. If that would happen,
it would mean that somewhere the supply wasn't increased while increasing the balance of an account.

* Update frame/assets/src/functions.rs

* Update frame/assets/src/functions.rs

* Update frame/assets/src/functions.rs

Co-authored-by: default avatarShawn Tabrizi <[email protected]>

* FMT

Co-authored-by: default avatarShawn Tabrizi <[email protected]>
      2541efdb
    • Bastian Köcher's avatar
      cumulus-companion: Fix CI when there is no Polkadot companion (#11280) · 914db49d
      Bastian Köcher authored 
      This tries to fix the CI if there is no polkadot companion. Currently we don't update Polkadot
master in Cumulus, which means we may use some old commit that isn't compiling with the latest
Substrate master anymore. This can happen if there was a pr that had a companion in Polkadot, but no
companion was required for Cumulus. Then Cumulus will still point to some old Polkadot commit that
isn't compiling anymore with the latest Substrate commit. So, we need to tell the script to use the
latest master of Polkadot. If there is a companion for Polkadot, it would simply override the extra
dependency patch later on.
      914db49d
    • Nazar Mokrynskyi's avatar
      More efficient identity and multiplier weight to fee (#11226) · 53994691
      Nazar Mokrynskyi authored
      53994691
  5. Apr 22, 2022
    • Bastian Köcher's avatar
      BABE: Fix aux data cleaning (#11263) · 53575a95
      Bastian Köcher authored 
      With the latest optimizations of the `FinalityNotification` generation, the aux data pruning started
to print a warning. The problem here was that we printed a warning and stopped the adding of blocks
to prune when we hit the `heigh_limit`. This is now wrong, as we could for example have two 512 long
forks and then we start finalizing one of them. The second fork head would be part of the stale
heads at some point (in the current implementation when we finalize second fork head number + 1),
but then we would actually need to go back into the past than `heigh_limit` (which was actually
last_finalized - 1). We now go back until we reach the canonical chain.

Also fixed some wrong comment that was added by be about the content of the `finalized` blocks in
the `FinalityNotification`.
      53575a95
    • dependabot[bot]'s avatar
      Bump tracing-core from 0.1.21 to 0.1.26 (#11258) · 02c7433b
      dependabot[bot] authored 
      

Bumps [tracing-core](https://github.com/tokio-rs/tracing) from 0.1.21 to 0.1.26.
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](https://github.com/tokio-rs/tracing/compare/tracing-core-0.1.21...tracing-core-0.1.26)

---
updated-dependencies:
- dependency-name: tracing-core
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: default avatardependabot[bot] <[email protected]>

Co-authored-by: default avatardependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
      02c7433b
  7. Apr 21, 2022
  9. Apr 20, 2022
  11. Apr 19, 2022
  13. Apr 18, 2022
  15. Apr 16, 2022
  17. Apr 15, 2022
  19. Apr 14, 2022
  21. Apr 13, 2022
  23. Apr 12, 2022
    • Qinxuan Chen's avatar
      Bump soketto to v0.7.1 (#11203) · 3fec1082
      Qinxuan Chen authored 
      

Signed-off-by: default avatarkoushiro <[email protected]>
      3fec1082
    • Denis_P's avatar
      CI: rename ambiguous jobs (#11207) · ba8beeed
      Denis_P authored
      ba8beeed
    • Bastian Köcher's avatar
      Finality notification: Optimize calculation of stale heads (#11200) · cc4b5c48
      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: default avatarAndré Silva <[email protected]>

* Do not include the last finalized block

* Rename function

* FMT

* Fix tests

* Update figure

Co-authored-by: default avatarAndré Silva <[email protected]>
      cc4b5c48
    • Xiliang Chen's avatar
      add has_identity (#11197) · f84fc598
      Xiliang Chen authored 
      

* add has_identity

* Update frame/identity/src/lib.rs

Co-authored-by: default avatarBastian Köcher <[email protected]>

* update

* update

Co-authored-by: default avatarBastian Köcher <[email protected]>
      f84fc598
  25. Apr 11, 2022
    • Koute's avatar
      Add new hardware and software metrics (#11062) · 8351ada6
      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`
      8351ada6
    • Bastian Köcher's avatar
      Prepare for rust stable 1.60 (#11138) · f517e57f
      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: default avataralvicsam <[email protected]>
Co-authored-by: default avatarAlexander Samusev <[email protected]>
      f517e57f