Skip to content
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

Disable report_invalid in the vendor'd transaction pool #2186

Closed

Conversation

wilwade
Copy link
Collaborator

@wilwade wilwade commented Oct 14, 2024

Goal

The goal of this PR is to separate into a separate PR the only change happening to the vender'd transaction pool

@@ -508,8 +508,12 @@ impl<Hash: hash::Hash + Member, Ex> BestIterator<Hash, Ex> {
impl<Hash: hash::Hash + Member, Ex> sc_transaction_pool_api::ReadyTransactions
for BestIterator<Hash, Ex>
{
fn report_invalid(&mut self, tx: &Self::Item) {
BestIterator::report_invalid(self, tx)
fn report_invalid(&mut self, _tx: &Self::Item) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm worried about side effects. Maybe we can do some tests using https://github.com/paritytech/polkadot-stps?tab=readme-ov-file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our e2e tests on testnet get close to that (and they were showing the issue) I think we could setup something like that as well for it.

@wilwade wilwade mentioned this pull request Oct 24, 2024
7 tasks
@wilwade wilwade closed this Oct 24, 2024
@wilwade wilwade deleted the fix/hack-transaction-pool branch October 29, 2024 18:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants