Avoid Dropping Upstream Items in mergeSource
#513
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.
From what I understand,
mergeSource
willawait
an item from upstream, and if successful,await
an item fromsrc0
. If there is no item insrc0
, the conduit terminates. This means that the item that was already taken from upstream is now lost (note the missing item4
in the output):This PR adds the already consumed item back using
leftover
, leading to the expected result:Disclaimer: I am pretty new to Conduit, so it is possible that I am either misunderstanding something or that there is a good reason for the current behavior of
mergeSource
, in which case, feel free to correct me.