Transaction pool: Ensure that we prune transactions properly (#8963)
* Transaction pool: Ensure that we prune transactions properly There was a bug in the transaction pool that we didn't pruned transactions properly because we called `prune_known`, instead of `prune`. This bug was introduced by: https://github.com/paritytech/substrate/pull/4629 This is required to have stale extrinsics being removed properly, so that they don't fill up the tx pool. * Fix compilation * Fix benches * ...
parent
f585bf1c
Showing
- substrate/client/transaction-pool/graph/benches/basics.rs 8 additions, 1 deletionsubstrate/client/transaction-pool/graph/benches/basics.rs
- substrate/client/transaction-pool/graph/src/listener.rs 3 additions, 7 deletionssubstrate/client/transaction-pool/graph/src/listener.rs
- substrate/client/transaction-pool/graph/src/pool.rs 14 additions, 1 deletionsubstrate/client/transaction-pool/graph/src/pool.rs
- substrate/client/transaction-pool/graph/src/validated_pool.rs 11 additions, 15 deletions...trate/client/transaction-pool/graph/src/validated_pool.rs
- substrate/client/transaction-pool/src/api.rs 17 additions, 3 deletionssubstrate/client/transaction-pool/src/api.rs
- substrate/client/transaction-pool/src/lib.rs 20 additions, 5 deletionssubstrate/client/transaction-pool/src/lib.rs
- substrate/client/transaction-pool/src/testing/pool.rs 78 additions, 35 deletionssubstrate/client/transaction-pool/src/testing/pool.rs
- substrate/test-utils/runtime/transaction-pool/src/lib.rs 19 additions, 1 deletionsubstrate/test-utils/runtime/transaction-pool/src/lib.rs
Please register or sign in to comment