-
Notifications
You must be signed in to change notification settings - Fork 39
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
Enclave: produce no batch if all tx failed #1698
Conversation
WalkthroughThe change involves a modification in the Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on X ? TipsChat with CodeRabbit Bot (
|
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.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (1)
- go/enclave/components/batch_executor.go (1 hunks)
Additional comments: 1
go/enclave/components/batch_executor.go (1)
- 213-219: The updated condition in the
ComputeBatch
method correctly implements the PR's objective by ensuring that a batch is only created if there are transactions to process after excluding the failed ones. This is a logical and efficient way to prevent the creation of empty batches.
if failForEmptyBatch && | ||
len(txReceipts) == 0 && | ||
len(ccReceipts) == 0 && | ||
len(transactionsToProcess) == 0 && | ||
len(transactionsToProcess)-len(excludedTxs) == 0 && | ||
len(crossChainTransactions) == 0 && | ||
len(messages) == 0 && | ||
len(transfers) == 0 { |
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.
Consider refactoring the ComputeBatch
method to reduce its cognitive complexity and improve maintainability. This could involve breaking down the method into smaller, more focused sub-methods.
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.
lgtm.
this is probably it.
I'm working on getting rid of that excluded txs thing
Why this change is needed
Avoid spamming empty batches when there is a rejected tx but no successful transactions.
PR checks pre-merging
Please indicate below by ticking the checkbox that you have read and performed the required
PR checks