Fix for concurrent exchanging on one client #230
Merged
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.
If we send requests fast enough client can mix frames of different queries. That leads to "Unknown portal" error (when one flow send
Sync
between othersBind
andExecute
) or "Source emitted more than one item" (when one flow sendSync
between othersExecute
andSync
- its result will receiveCommandComplete
from both queries).It can easely be fixed by changing concurrent subscribing to request
Publisher
s to concatmapping them.Should fix #207