fix(consensus)!: defer proposing txs with conflicting unversioned inputs #1125
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
fix(consensus)!: defer proposing txs with conflicting unversioned inputs
refactor: locks take into account if the requested input was versioned or not
Motivation and Context
A transaction may provide an unversioned input. In the multi-shard case, if this input is locked by another transaction, the first transaction should not be proposed until that lock is cleared.
How Has This Been Tested?
Manually, submitting transactions with conflicting unversioned inputs.
What process can a PR reviewer use to test or verify this change?
Submit transactions with transaction_generator and transaction_submitter. The default generated transactions use unversioned inputs.
Breaking Changes