-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
interop: implement rpc-behavior for UnaryCall() #6575
Conversation
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.
go.sum doesn't need to be updated like that, and please fix vet. You can run VET_SKIP_PROTO=1 ./vet.sh from the home directory to run the vet script. Also will need to run interop tests against this before merging to make sure this doesn't break anything.
hi @zasweq and @easwars fixed the
thank you for sharing the style guide as well, I will go through it |
It's got less to do with the runtime cost and more to do with cognitive cost when reading the code.
Are you referring to individual comments or separate PRs? It is not clear to me.
Reading through the whole thing in one go can be painful :) and not very useful. I'd recommend slowly incorporating those guidelines into your coding. |
@Aditya-Sood let us know if this PR is ready for review again. |
@arvindbr8 yes I've asked for review comments here #6575 (comment) |
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.
One final thing
interop/xds/server/server.go
Outdated
mdRPCBehavior := getMetadataValues(ctx, rpcBehaviorMDKey) | ||
var rpcBehaviorMetadata []string | ||
for _, val := range mdRPCBehavior { | ||
splitVals := strings.Split(val, ",") |
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.
Hello, we discussed this in our gRPC-Go team meeting today. The behavior we agreed upon is actually the trimming of the whitespace, as Java does it. Sorry for the hassle, I know I had you switch it earlier in this PR. Can you please switch it back then I'll go ahead and merge this. After merging, I'll file an issue in the gRPC repo to switch interop tests over to use gRPC-Go as the server. Thanks!
hi @zasweq, could you please clarify on the above query? |
Vet proto seems to be failing, this looks good to merge though. Can you please rebase onto master and once it passes I'll merge? |
Pending header values: "sleep", "keep-open", "success-on-retry-attempt" and "hostname"
Uses a switch statement instead of the previous if-else-if ladder for behavior matching
…ader And minor code review refactors
a62020c
to
304a7d3
Compare
hi @zasweq, vet proto is passing after the rebase |
Implements the spec found at: https://github.com/grpc/grpc/blob/master/doc/xds-test-descriptions.md#server
Fixes #6288
RELEASE NOTES: none