-
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
metadata: Remove NewContext and FromContext for gRFC L7 #1392
Conversation
Can someone check if this is related to this change? |
Yes. This PR is a breaking change. grpc-gateway needs to be updated to use metadata.FromIncomingContext or FromOutgoingContext, whichever is appropriate based upon its usage. |
NewContext has been deprecated in favor of NewOutgoingContext. See grpc/grpc-go#1392 Change-Id: Ieb3491f032cdaa1eb59878451c29fefe71efada0
grpc/grpc-go#1392 has removed metadata.NewContext and metadata.FromContext, so (locally) change invocations in our vendored etcd code.
grpc/grpc-go#1392 has removed metadata.NewContext and metadata.FromContext, so (locally) change invocations in our vendored etcd code.
metadata.FromContext has been deprecated, for our use case we need to call metadata.FromIncomingContext instead. grpc/grpc-go#1392 grpc/proposal@c8857c2
grpc/grpc-go#1392 has removed metadata.NewContext and metadata.FromContext, so (locally) change invocations in our vendored etcd code.
grpc/grpc-go#1392 has removed metadata.NewContext and metadata.FromContext, so (locally) change invocations in our vendored etcd code.
This breaks API, why there were no major version bump? |
We don't have a policy of bumping the major version number on API changes. gRPC 2.0 is reserved for when wire protocol changes are made that will require a new version of gRPC across languages. We have changed our API in 1.x and expect to do so in upcoming releases as well. This change was broadcast months in advance through all means available (grpc-io mailing list, proposals repo, here). And it was listed under "API Changes" in the release notes of 1.6. Sorry for the breakage this caused, but I don't think there's anything else we could have done here. EDIT: I locked this thread because I don't think it's productive to have any further general discussion about versioning or API breakages here. Please file a new issue against the repo if you want to discuss our policies/etc. |
As an update to my comment above:
|
gRFC: grpc/proposal#25