Skip to content
  1. Apr 27, 2022
  2. 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
  4. 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
  5. Apr 21, 2022
  6. Apr 20, 2022
  7. Apr 19, 2022
  8. Apr 18, 2022
  9. Apr 16, 2022
  10. Apr 15, 2022
  11. Apr 14, 2022
  12. Apr 13, 2022