You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
release 3.2.0rc1. I am also getting the same error on releases 2.2.0, 3.0.0, and 3.1.0. Not on release 2.1.0.
Have you found anything relevant by searching the web?
The following issues seem related, but I couldn't understand whether this is a duplicate of those, especially considering the release versions: #10484 #10590
The text was updated successfully, but these errors were encountered:
This is caused by the (regrettable) difference between ProtoInfo#getDirectProtoSources() and ProtoInfo#getOriginalDirectProtoSources() [1]. Depending on the version of Protobuf, this is probably broken since Bazel 1.0 (around Protobuf < 3.9.x) or even earlier Bazel versions (Protobuf > 3.10.x).
Also, there may be a problem if a deps only (alias/facade) library is blacklisted. cc_proto_library already blacklists the transitive (original) sources because of that.
Description of the problem / feature request:
proto_lang_toolchain does not exclude blacklisted_protos
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Our setup does something like this:
When we run https://cs.opensource.google/bazel/bazel/+/master:src/main/java/com/google/devtools/build/lib/rules/java/OneVersionCheckActionBuilder.java on the built jar, we are seeing one-version violations on all the @@com_google_protobuf protos for releases newer than 2.1.0.
What operating system are you running Bazel on?
OS X
What's the output of
bazel info release
?release 3.2.0rc1. I am also getting the same error on releases 2.2.0, 3.0.0, and 3.1.0. Not on release 2.1.0.
Have you found anything relevant by searching the web?
The following issues seem related, but I couldn't understand whether this is a duplicate of those, especially considering the release versions:
#10484
#10590
The text was updated successfully, but these errors were encountered: