fix(engine): finalize errors (e.g. dangling bucket) reject the main transaction only #1109
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Extracted the
validate_finalized
check invocation from theStateTracker
into theTransactionProcessor
, to be done automatically at the end of allinstructions
andfee_instructions
.Motivation and Context
Currently, when the main instruction set has a dangling bucket (or another finalizing error), the whole transaction is rejected. What we want instead is only the main transaction being rejected, and the fees are still paid (
AcceptFeeRejectRest
)How Has This Been Tested?
New unit test (
dangling_bucket_pay_fees
) in the engine to reproduce this scenarioWhat process can a PR reviewer use to test or verify this change?
Reproduce a dangling bucket error and check that the fees are paid
Breaking Changes