fix: fix endpoints parsing in Go Client #444
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
|
@aaron-ai Hello, it's seems some network error on CI, could you help rerun CI and help review the PR, thanks |
|
@imp2002 Great! Extracting multiple addresses from endpoints is the first step in solving this problem. In fact, the specified implementations of gRPC allow a client/stub to bind to multiple IP addresses. For example, in C++, you can refer to here, and in Java, you can refer to the implementation of IpNameResolverFactory. Can you help us confirm how to implement this in Go? |
|
OK, I'll try it. |
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.
Fix: #377