-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
api: When forwarding from Listener onAddresses to Listener2 continue to use onResult #11666
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
…ization context to call it from inside of the synchronization context. Fixes grpc#11662.
ejona86
reviewed
Nov 5, 2024
core/src/main/java/io/grpc/internal/ManagedChannelImplBuilder.java
Outdated
Show resolved
Hide resolved
…d from sync context.
kannanjgithub
changed the title
api: Listener2.onResult2 can only be called from within the synchronization context
api: Use synchronization context when forwarding from Listener onAddresses to Listener2 onResult2
Nov 5, 2024
ejona86
approved these changes
Nov 5, 2024
kannanjgithub
changed the title
api: Use synchronization context when forwarding from Listener onAddresses to Listener2 onResult2
api: When forwarding from Listener onAddresses to Listener2 continue to use onResult
Nov 5, 2024
Fixes #11662 |
ejona86
added
the
TODO:backport
PR needs to be backported. Removed after backport complete
label
Nov 12, 2024
kannanjgithub
added a commit
to kannanjgithub/grpc-java
that referenced
this pull request
Nov 14, 2024
…to use onResult (grpc#11666) When forwarding from Listener onAddresses to Listener2 continue to use onResult and not onResult2 because the latter requires to be called from within synchronization context and it breaks existing code that didn't need to do so when using the old Listener interface.
kannanjgithub
added a commit
that referenced
this pull request
Nov 14, 2024
…to use onResult (#11666) (#11688) When forwarding from Listener onAddresses to Listener2 continue to use onResult and not onResult2 because the latter requires to be called from within synchronization context and it breaks existing code that didn't need to do so when using the old Listener interface.
ejona86
removed
the
TODO:backport
PR needs to be backported. Removed after backport complete
label
Nov 27, 2024
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 forwarding from Listener onAddresses to Listener2 continue to use onResult and not onResult2 because the latter requires to be called from within synchronization context and it breaks existing code that didn't need to do so when using the old Listener interface.