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-1.45.1 does not compile with protobuf-3.20.0 #29297

Closed
coryan opened this issue Apr 2, 2022 · 1 comment
Closed

gRPC-1.45.1 does not compile with protobuf-3.20.0 #29297

coryan opened this issue Apr 2, 2022 · 1 comment

Comments

@coryan
Copy link
Contributor

coryan commented Apr 2, 2022

What version of gRPC and what language are you using?

C++, gRPC-1.45.1

What operating system (Linux, Windows,...) and version?

The problem manifests in Linux, Windows, and macOS.

What runtime / compiler are you using (e.g. python version or version of gcc)

This is not compiler or runtime specific.

What did you do?

Try to compile gRPC-1.45.1 with Protobuf-3.20.0. Using this small program

What did you expect to see?

A successful build.

What did you see instead?

Bazel errors:

ERROR: /usr/local/google/home/coryan/.cache/bazel/_bazel_coryan/1597fbe7e0d6911d6fc0820b75877b84/external/com_envoyproxy_protoc_gen_validate/validate/BUILD:28:17: Label '@com_google_protobuf//:protobuf_python' is duplicated in the 'deps' attribute of rule 'validate_py'
ERROR: /usr/local/google/home/coryan/.cache/bazel/_bazel_coryan/1597fbe7e0d6911d6fc0820b75877b84/external/envoy_api/envoy/config/core/v3/BUILD:7:18: Target '@com_envoyproxy_protoc_gen_validate//validate:validate_proto' contains an error and its package is in error and referenced by '@envoy_api//envoy/config/core/v3:pkg'
ERROR: Analysis of target '//:test' failed; build aborted: 
INFO: Elapsed time: 1.426s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (35 packages loaded, 9 targets configured)

Anything else we should know about your project / environment?

@gnossen
Copy link
Contributor

gnossen commented Apr 4, 2022

This looks like an issue between Protobuf and the Envoy project. Envoy is using the protobuf repo's (private, internal) py_proto_library rule here. It looks like this might have been caused by this PR on protobuf.

In fact, it looks like they are aware of the problem and have already rolled the PR back. Going ahead and closing as this isn't really a gRPC issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants