Skip to content
  1. Jun 16, 2020
    • Demi Obenour's avatar
      Add IPC support (#6348) · 69070184
      Demi Obenour authored 
      This is useful for both security and performance reasons. IPC is faster
than TCP, and it is subject to OS access controls.
      69070184
  3. Jun 12, 2020
    • Bastian Köcher's avatar
      Fix transaction pool event sending (#6341) · 384be7e2
      Bastian Köcher authored 
      This pr fixes a bug with the transaction pool not sending certain events
like finalized and also fixes the order of events. The problem with the
finalized event was that we did not extracted pruned extrinsics if there
were not ready transactions in the pool. However this is wrong, if we
have a re-org, a tx is clearly not ready anymore and we still need to
send a pruned event for it because it is in a new block included. This
also lead to sending "ready" events and tx being re-validated. The
listener also only send the "finalized" event if it has seen a block as
being included, which did not happen before with the old code.

The second fix of the pr is the order of events. If we prune and retract the
same transaction in the same block, we first need to send the "retract"
event and after that the "pruned" event, because finalization takes
longer and this would lead to the UI showing "retract" while it actually
is included.
      384be7e2
    • 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
  5. Jun 11, 2020
  7. Jun 10, 2020
  9. Jun 09, 2020
  11. 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
      client/api: fix possible deadlock when comparing with itself (#6277) · 4a560614
      Boqin Qin authored
      4a560614
    • 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
  13. Jun 06, 2020
  15. Jun 05, 2020
  17. Jun 04, 2020
  19. Jun 03, 2020
  21. Jun 02, 2020