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

grpc code generator in v1.4.0 (and master) is outdated #1111

Closed
menghanl opened this issue May 1, 2020 · 3 comments · Fixed by #1113
Closed

grpc code generator in v1.4.0 (and master) is outdated #1111

menghanl opened this issue May 1, 2020 · 3 comments · Fixed by #1113

Comments

@menghanl
Copy link
Contributor

menghanl commented May 1, 2020

What version of protobuf and what language are you using?
v1.3.5, v1.4.0 and master


Latest commit on tag v1.4.0 is from Nov 2018

https://github.com/golang/protobuf/tree/v1.4.0/protoc-gen-go/grpc
image


Latest commit from v1.3.5 is from Jan 2020

https://github.com/golang/protobuf/tree/v1.3.5/protoc-gen-go/grpc
image


Master is missing commits, too

https://github.com/golang/protobuf/tree/master/protoc-gen-go/grpc
image

@dsnet
Copy link
Member

dsnet commented May 1, 2020

The github.com/golang/protobuf/protoc-gen-go/grpc package is dead code. The underlying implementation for grpc is in github.com/golang/protobuf/internal/gengogrpc, which at the time created was a direct copy of the code in google.golang.org/protobuf/cmd/protoc-gen-go-grpc/internal_gengogrpc.

The commit you think is missing was simultaneously committed to the new implementation here.

@menghanl
Copy link
Contributor Author

menghanl commented May 1, 2020

This will break users using grpc as a library (instead of using the binary generator). I'm verifying with the user now, in grpc/grpc-go#3591.

But even though using the library isn't expected, was there any particular reason to have outdated code there?
It's an exported package (probably should have been, but..), and I don't see any reason to break it.

@dsnet
Copy link
Member

dsnet commented May 1, 2020

This will break users using grpc as a library (instead of using the binary generator).

If that's the case, then that use case is unfortunately unsupported. Any uses of generator as a library has explicitly been stated to be outside our compatibility policy. That said, we may consider making the grpc package identical to what it was in v1.3.5 even though it's on the chopping block for being removed in the future.

dsnet added a commit that referenced this issue May 4, 2020
Even through the grpc package is excluded from our compatibility agreement,
the v1.4.0 release accidentally reverted the package to an older revision.
Update this code to be identical to the v1.3.5 release (barring non-semantic
documentation changes).

Fixes #1111
dsnet added a commit that referenced this issue May 4, 2020
Even through the grpc package is excluded from our compatibility agreement,
the v1.4.0 release accidentally reverted the package to an older revision.
Update this code to be identical to the v1.3.5 release (barring non-semantic
documentation changes).

Fixes #1111
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 a pull request may close this issue.

2 participants