feat(reliability): orders transaction queue -- bump packages #392
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.
Context: Traders have encountered an issue where canceling stateful orders can be unreliable. Root cause appears to be broadcast errors related to sequence numbers when placing or canceling stateful orders in rapid succession.
To address this, a transaction queue is added in abacus for placing and canceling stateful orders, so that the transactions are done sequentially but without blocking UI interactions.
In v4-clients, placing and canceling long term and conditional orders now default to use Method.BroadcastTxCommit. Thus the action will only complete after tx has been fully committed.
To test: