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.
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
transport,grpc: Integrate delegating resolver and introduce dial options for target host resolution #7881
base: master
Are you sure you want to change the base?
transport,grpc: Integrate delegating resolver and introduce dial options for target host resolution #7881
Changes from 44 commits
619dcd4
65b33bd
94364e2
9f6a067
5ce86d0
fbef3a4
342c332
8726188
1cfb089
32d9de5
34b902f
11c8fb1
b4c9980
93fc3e1
e22ad1d
b515565
7ae2797
5ce4658
a292b63
4483e95
d4f6215
333a68c
cacf058
7c5b1b3
cb6b09c
ff05ee3
104cd18
fb23cca
ef927ce
bc5efc3
876f09e
3e20010
6827a62
9acd8de
8f5055e
bbd7f02
128da2c
7cb9ec8
0d055b3
07b9344
f75662d
2df2f2e
9e52674
7d230bc
27cc055
227c748
bdbe501
8a43a91
a73d511
0c154cf
d396d31
fd088d1
32fa83c
382bcb1
69037b0
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This comparison with a zero-initialized Userinfo looks a little off to me. Should this field in
opts
be a pointer instead to determine whether it was set intentionally?Or should it check if either
Username()
orPassword()
are non-empty?I'm not sure exactly what the right behavior is, but this seems questionable, as it's including any unexported fields in the comparison.
Related but potential existing problem to investigate: what if username is set but password is not? Is that valid? If so, is the proper behavior to encode it as
username:
, as it does currently, or should the:
be omitted?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The RFC doesn't clearly mention what is the correct syntax if password is absent , so I think either way should be fine, but adding a semicolon like
username:
would be more explicit in indication username has ended and the password is empty.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have added a
UserSet
option as changing it to a pointer can allow the caller to modify the use info.