Skip to content
  1. Jun 12, 2020
    • André Silva's avatar
      client: use appropriate ExecutionContext for initial sync / regular import (#6180) · 0dc66347
      André Silva authored
      * client: use appropriate ExecutionContext for sync/import
      
      * client: remove dead code
      
      * client: ExecutionContext: distinguish between own and foreign imports
      
      * client: fix cli parameter doc
      
      * Revert "client: ExecutionContext: distinguish between own and foreign imports"
      
      This reverts commit 0fac1152.
      
      * primitives: add docs for ExecutionContext
      
      * cli: execution strategy docs
      
      * cli: use different execution context for importing block on validator
      
      * cli: remove defaults from execution context flags
      0dc66347
  2. Jun 11, 2020
  3. Jun 10, 2020
  4. Jun 09, 2020
  5. Jun 08, 2020
    • Nikolay Volf's avatar
      Fix transaction pool & network issues (#6288) · 85cd5569
      Nikolay Volf authored
      * fix & tweaks
      
      * address review
      
      * line width
      85cd5569
    • Benjamin Kampmann's avatar
      Intent to release rc3 (#6290) · e287915e
      Benjamin Kampmann authored
      e287915e
    • Subsocial's avatar
      Fix typo: eror -> error (#6293) · f2c8b88d
      Subsocial authored
      f2c8b88d
    • Hernando Castano's avatar
      Use Subscription Manager from `jsonrpc-pubsub`: The Sequel (#6254) · 3cb05a1e
      Hernando Castano authored
      
      
      * Bump jsonrpc pubsub, core, http, and ws
      
      Right now these are the packages which _need_ to be updated
      so I can just the latest `jsonrpc-pubsub` code. Once a release
      it cut upstream the rest of the dependencies should be updated
      as well.
      
      * Use jsonrpc-pubsub's SubscriptionManager
      
      This places sc-rpc-api::Subscriptions
      
      * Bump jsonrpc-core outside of sc-rpc-*
      
      * Update client/rpc tests
      
      Right now one of the `author` tests is failing, I
      need to think a bit about how best to fix it.
      
      * Remove Subscriptions manager
      
      There's no need for this implementation since we're
      using the one from `jsonrpc-pubsub` now
      
      * Fix author RPC test
      
      This test used to check for a numerial subscription ID,
      whereas now it uses a string based ID which is the default
      provided by `jsonrpc-pubsub`'s subscription manager.
      
      * Remove unused NumericIdProvider
      
      * Add missing bracket
      
      Removed one too many with that last one, lol
      
      * Bump `jsonrpc` to v14.2
      
      There's an exception though. `jsonrpc-derive` cannot be bumped
      past v14.0.5 just yet since it has a dependency on `quote` pinned
      to v1.0.1. This means that at the moment it won't build on Substrate
      since it's using v1.0.3.
      
      * Track `jsonrpc-derive` master branch
      
      * Bump `quote` version to v1.0.6
      
      * Bump `jsonrpc-derive` to v14.2.1
      
      This includes support for `quote` v1.0.6
      
      * Use exact version for jsonrpc crates
      
      Doing this to make sure any updates in jsonrpc don't
      accidently trickle down to Polkadot.
      
      Co-authored-by: default avatarAndré Silva <[email protected]>
      3cb05a1e
    • pscott's avatar
      Make all features explicit (#6267) · a5bf77de
      pscott authored
      
      
      * make all features explicit
      
      * Change to -feature suffix to with- prefix
      
      * Add newline at the end of the Cargo.toml file
      
      * Remove rhd feature
      
      * Remove some features from Cargo.toml
      
      * Remove test-helpers feature in tx pool
      
      * Return db_open_error("with-"..
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Rename subdb feature to with-subdb
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      
      * Remove 'strict' feature and cfg_attr
      
      * Check for with-subdb feature instead of subdb
      
      Co-authored-by: default avatarBastian Köcher <[email protected]>
      a5bf77de
    • Boqin Qin's avatar
    • Bastian Köcher's avatar
      Fix transaction pruning in tx-pool (#6276) · 9fe0da54
      Bastian Köcher authored
      The `tree_route` generated by the import notification is only from the
      old best block to the new best parent. This means, it does not contain
      the new best block in `enacted()`. We need to prune the transactions of
      the new best block "manually" to fix this bug.
      
      Besides that, this pr also changed the `id` parameter of the `NewBlock`
      chain event to `hash`. The hash of a block is unique in contrast to the
      block number. (Block id can either be number or hash)
      9fe0da54
  6. Jun 06, 2020
  7. Jun 05, 2020
  8. Jun 04, 2020
  9. Jun 03, 2020
  10. Jun 02, 2020
  11. Jun 01, 2020