Fix incorrect request-n management for Publisher.multicast()
#1083
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.
Motivation
Produces the output:
This shows that
multicastToExactly()
is not requesting more thanqueueSize()
items unless the subscriber requests more.Modification
MulticastUtils.updateRequestN()
based ondrainCount
. Since drained item count is already included inemitted
, this additional constraint is not required.SubscriberUtils.calculateSourceRequested()
did not handle the case whenemitted > sourceRequested
resulting in higher request-n numbers. For cases like groupBy/multicast when items maybe buffered before they are requested by the subscriber, we need to handleemitted > sourceRequested
.Result
multicastToExactly()
correctly requests all items from the original source.