-
Notifications
You must be signed in to change notification settings - Fork 766
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
txpool api
: remove_invalid
call improved
#6661
base: master
Are you sure you want to change the base?
Conversation
&self, | ||
at: Option<<Self::Block as BlockT>::Hash>, | ||
invalid_tx_errors: &[(TxHash<Self>, Option<sp_blockchain::Error>)], | ||
) -> Vec<Arc<Self::InPoolTransaction>>; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could also keep old function remove_invalid
and add new one, with no optional error/block parameters. Really no strong opinion here.
I also think that triggering invalid event in case of removal the transaction via RPC call is (maybe) undesirable - so maybe we should have pure remove function (which would trigger Dropped
, IMO it makes more sense). Any thoughts?
txpool api
: remove invalid call improved
txpool api
: remove invalid call improvedtxpool api
: remove_invalid
call improved
All GitHub workflows were cancelled due to failure one of the required jobs. |
All GitHub workflows were cancelled due to failure one of the required jobs. |
Currently the transaction which is reported as invalid by a block builder (or
removed_invalid
by other components) is silently skipped.This PR improves this behavior. The transaction pool
report_invalid
function now accepts optional error associated with every reported transaction, and also the optional block hash which provides hints how reported transaction shall be handled. The following API change is proposed:polkadot-sdk/substrate/client/transaction-pool/api/src/lib.rs
Lines 293 to 310 in 8c8e033
Depending on error, the transaction pool can decide if transaction shall be removed from the view only or entirely from the pool. Invalid event will be dispatched if required.
fixes: #6008