This repository was archived by the owner on Mar 9, 2026. It is now read-only.
fix: get channel target for a gRPC request - #1339
Merged
mukund-ananthu merged 5 commits intoJan 29, 2025
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
ohmayr
force-pushed
the
fix-pubsub-target-issue
branch
from
df9cb1e to
135038e
Compare
January 28, 2025 20:54
Copy link
Copy Markdown
Contributor
|
@ohmayr Could you please fix the unit tests. |
Sorry, something went wrong.
Comment thread
tests/unit/pubsub_v1/publisher/test_publisher_client.py
mukund-ananthu
approved these changes
Jan 29, 2025
ohmayr
force-pushed
the
fix-pubsub-target-issue
branch
from
591a7a9 to
576a948
Compare
January 29, 2025 20:56
parthea
approved these changes
Jan 29, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Reviewers
2 more reviewersAssignees
3 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.
Depends on #1348.
This is a workaround to resolve the issue for accessing the gRPC channel target: b/388826364
Refer to grpc/grpc#38519 for a more stable solution.