8000 api: When forwarding from Listener onAddresses to Listener2 continue to use onResult by kannanjgithub · Pull Request #11666 · grpc/grpc-java · GitHub

api: When forwarding from Listener onAddresses to Listener2 continue to use onResult#11666

Merged

kannanjgithub merged 2 commits intogrpc:masterfrom

kannanjgithub:onresult2synccontext

Nov 5, 2024

Commits on Nov 5, 2024

Fix NameResolvers calling Listener2.onResult2 outside of the synchronization context to call it from inside of the synchronization context.
kannanjgithub
committed
Remove unnecessary changes as start and resolve etc are already called from sync context.
kannanjgithub
committed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

api: When forwarding from Listener onAddresses to Listener2 continue to use onResult#11666

api: When forwarding from Listener onAddresses to Listener2 continue to use onResult#11666
kannanjgithub merged 2 commits intogrpc:masterfrom
kannanjgithub:onresult2synccontext

Commits on Nov 5, 2024

Fix NameResolvers calling Listener2.onResult2 outside of the synchronization context to call it from inside of the synchronization context.

Remove unnecessary changes as start and resolve etc are already called from sync context.

api: When forwarding from Listener onAddresses to Listener2 continue to use onResult#11666kannanjgithub merged 2 commits intogrpc:mastergrpc/grpc-java:masterfrom kannanjgithub:onresult2synccontextkannanjgithub/grpc-java:onresult2synccontextCopy head branch name to clipboard

Commits

Commits on Nov 5, 2024

Fix NameResolvers calling Listener2.onResult2 outside of the synchronization context to call it from inside of the synchronization context.

Remove unnecessary changes as start and resolve etc are already called from sync context.

api: When forwarding from Listener onAddresses to Listener2 continue to use onResult#11666
kannanjgithub merged 2 commits intogrpc:masterfrom
kannanjgithub:onresult2synccontext