Skip to content
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

bugfix: reflect upstream api change. #359

Merged
merged 1 commit into from
Apr 17, 2017

Conversation

tmc
Copy link
Collaborator

@tmc tmc commented Apr 17, 2017

metadata.NewContext now is a synonym for metadata.NewOutgoingContext. Call NewIncomingContext instead.

Fixes #358

metadata.NewContext now is a synonym for metadata.NewOutgoingContext. Call NewIncomingContext instead.
@tmc tmc requested review from yugui and achew22 April 17, 2017 04:12
@tmc
Copy link
Collaborator Author

tmc commented Apr 17, 2017

we don't currently have a more "e2e" test to show this context propagation over an actual call so this wasn't caught in test. I'd like for us to have that but also want to get a release out that is compatible with upstream grpc-go.

@achew22
Copy link
Collaborator

achew22 commented Apr 17, 2017

+1 to e2e testing. Also LGTM.

@achew22 achew22 merged commit eaa3c30 into grpc-ecosystem:master Apr 17, 2017
@tmc tmc deleted the tmc.contextfix branch April 17, 2017 05:39
adasari pushed a commit to adasari/grpc-gateway that referenced this pull request Apr 9, 2020
metadata.NewContext now is a synonym for metadata.NewOutgoingContext. Call NewIncomingContext instead.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants