Single#concat(Publisher) invalid demand hang #1230
Merged
Conversation
This file contains 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
Motivation: If invalid demand is received by the Single#concat(Publisher) operator before the single completed the invalid demand may be overwritten by a subsequent request instead of propagating an error. Modifications: - Invalid demand should cancel the subscription and propagate an error. Result: Single#concat(Publisher) is more robust and follows rule 3.9 of the reactive streams spec.
idelpivnitskiy
approved these changes
Nov 24, 2020
tkountis
approved these changes
Nov 26, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
If invalid demand is received by the Single#concat(Publisher) operator
before the single completed the invalid demand may be overwritten by a
subsequent request instead of propagating an error.
Modifications:
Result:
Single#concat(Publisher) is more robust and follows rule 3.9 of the
reactive streams spec.