Skip to content
  1. Jul 17, 2020
    • Gavin Wood's avatar
      identity: Don't let subs be re-registered (#6667) · 640dd1a0
      Gavin Wood authored 
      

* Fixes and tests

* Don't set subs be re-registered.

Also allow subs to de-register themselves and collect the deposit.

Also allow individual registering and removal of subs.

* Make it build

* Update frame/identity/src/lib.rs

Co-authored-by: default avatarjoe petrowski <[email protected]>

* Tests

* Add benchmarks

* Add some reasonable weights

* Docs

Co-authored-by: default avatarjoe petrowski <[email protected]>
      640dd1a0
    • Max Inden's avatar
      .maintain/monitoring/alerting-rules: Remove HighCPUUsage alert (#6648) · 81e6a0cb
      Max Inden authored 
      The `HighCPUUsage` alert is based on the `cpu_usage_percentage` metric.
Instead of exposing the overall CPU usage in percent, the metric exposes
the per core usage summed over all cores.

This commit removes the alert for two reasons:

1. Substrate itself does not expose the core count and thus one can not
alert based on the `cpu_usage_percentage` metric.

2. Alerting based on CPU usage is generic and not specific to Substrate
or Blockchains. Thus any CPU usage alert suffice.
      81e6a0cb
  3. Jul 16, 2020
  5. Jul 15, 2020
  7. Jul 14, 2020
  9. Jul 13, 2020
    • Bastian Köcher's avatar
      Check that `serde` is present in `sc-chain-spec-derive` (#6636) · 60e3a693
      Bastian Köcher authored 
      We should check that `serde` is present when using
`sc-chains-spec-derive`, because we require this for the generated
struct. This also switches the generated `derive` instruction to import
`Serialize`/`Deserialize` by path to not require the user to import
these derive macros.
      60e3a693
  11. Jul 12, 2020
    • Bastian Köcher's avatar
      Make signature batching use specialized methods (#6616) · b0eefebc
      Bastian Köcher authored 
      It was a mistake to use the `*_verify` methods for signature batching.
This pr move the signature batching into their own functions. This is
required, because otherwise transaction signature verification infers
with other signature verifications.

This pr also temporarily disables signature batching. The functionality
stays, but we need to make sure that all nodes have the new runtime
interface, before we can bring back signature batching.
      b0eefebc
    • Kian Paimani's avatar
      Remove duplicate comments (#6638) · b5280cf9
      Kian Paimani authored
      b5280cf9
  13. Jul 11, 2020
  15. Jul 10, 2020
  17. Jul 09, 2020
  19. Jul 08, 2020
    • Shawn Tabrizi's avatar
      Add `WeightInfo` to all pallets with benchmarks. (#6575) · e824e8ab
      Shawn Tabrizi authored 
      * Start adding weight info

* More weightinfo

* finish weight info

* more fixes

* inital update of node runtime

* fix the rest of the compilation

* update balances

* add docs

* fix balances tests

* Fix more tests

* Fix compile

* Fix pallet-evm tests
      e824e8ab
    • Bastian Köcher's avatar
      Improve transaction submission (#6599) · d076f470
      Bastian Köcher authored 
      * Improve transaction submission

Before this pr the transaction pool validated each transaction, even if
the transaction was already known to the pool. This pr changes the
behavior to first check if we are already aware of a transaction and
thus, to only validate them if we don't know them yet. However, there is
still the possibility that a given transaction is validated multiple
times. This can happen if the transaction is added the first time, but
is not yet validated and added to the validated pool.

Besides that, this pr fixes the wrong metrics of gossiped transactions
in the network. It also moves some metrics to the transaction pool api,
to better track when a transaction actually is scheduled for validation.

* Make sure we don't submit the same transaction twice from the network concurrently

* Remove added listener call

* Feedback

* Ignore banned on resubmit
      d076f470