fix(api): Fix extra DB connection acquisition during tx submission #1793
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.
What ❔
Currently,
TxSender::submit_tx()
on the main node acquires 2 DB connections at the same time: one explicitly, and another in batch fee input provider. This PR eliminates this.Also, propagates errors in batch fee input provider, so that they don't lead to panics.
Why ❔
Holding multiple DB connections at the same time can lead to connection starvation, or at worst case (temporary) deadlocks.
Checklist
zk fmt
andzk lint
.zk spellcheck
.zk linkcheck
.