Do not duplicate demand in BroadcastDispatcher#319
Merged
josevalim merged 1 commit intoJul 15, 2025
Merged
Conversation
Since 5d8193e, the BroadcastDispatcher can send demand upstream even if its consumers did not request that many events. Because `waiting` is set to 0 when a new subscriber subscribes, the demand is repeated when the new subscriber asks for events. I am fixing this by introducing a new counter in state - the number of requested but not yet delivered events. The dispatcher now does not send upstream demand if the demand can be satisfied by the requested events (and sends a lower demand if it can be satisfied partially). Fixes elixir-lang#318.
xxdavid
commented
Jul 15, 2025
|
|
||
| {:ok, 10, disp} = D.ask(10, {pid2, ref2}, disp) | ||
| assert disp == {[{0, pid2, ref2, nil}], 10, expected_subscribers} | ||
| {:ok, 0, disp} = D.ask(10, {pid2, ref2}, disp) |
Contributor
Author
There was a problem hiding this comment.
Note that here (and also at line 155) I am reverting the IMO incorrect change in assertions in 5d8193e.
Member
|
Thank you, I believe this is indeed the correct fix and it was really well done. I will play with a couple more things locally and then do a new release |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Since 5d8193e, the BroadcastDispatcher can send demand upstream even if its consumers did not request that many events. Because
waitingis set to 0 when a new subscriber subscribes, the demand is repeated when the new subscriber asks for events.I am fixing this by introducing a new counter in state - the number of requested but not yet delivered events. The dispatcher now does not send upstream demand if the demand can be satisfied by the requested events (and sends a lower demand if it can be satisfied partially).
Fixes #318.
Feel free to close this pull request if you come up with a better solution.