fix: always initialize iterator state in RpcOutputStreamController #661
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
jsaguet
force-pushed
the
fix/initialize-it-state
branch
from
1c6a89e to
3f28e29
Compare
jsaguet
changed the title
jsaguet
force-pushed
the
fix/initialize-it-state
branch
from
3f28e29 to
307e03e
Compare
jsaguet
force-pushed
the
fix/initialize-it-state
branch
from
307e03e to
a4b3689
Compare
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.
When creating an RpcOutputStreamController in an interceptor, notifying a message synchronously drops the message because the async iterable is not yet subcribed to.
This PR solves this problem and addresses the issue #650