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
go_proto_library: missing strict dependencies on WKTs with protoc 3.14 #2721
Comments
Merged
1 task
This appears to be the culprit of why updating protobuf to 3.14 fails in envoyproxy/envoy. |
jayconrod
pushed a commit
to jayconrod/rules_go
that referenced
this issue
Nov 30, 2020
Since protobuf 3.14, the Well Known Types declare APIv2 package paths, which means generated code that imports them will import APIv2 packages. This PR is intended to be cherry-picked to the 0.23 and 0.24 release branches. It may slow down builds, since both APIv1 and APIv2 packages will be compiled; we can't tell which is needed during analysis. For bazelbuild#2721
jayconrod
pushed a commit
to jayconrod/rules_go
that referenced
this issue
Nov 30, 2020
These should not be imported in generated code when protobuf 3.14 or higher is used. protobuf 3.14.0 will be the minimum supported version for rules_go 0.25.0. Fixes bazelbuild#2721
jayconrod
pushed a commit
that referenced
this issue
Dec 1, 2020
Since protobuf 3.14, the Well Known Types declare APIv2 package paths, which means generated code that imports them will import APIv2 packages. This PR is intended to be cherry-picked to the 0.23 and 0.24 release branches. It may slow down builds, since both APIv1 and APIv2 packages will be compiled; we can't tell which is needed during analysis. For #2721
jayconrod
pushed a commit
that referenced
this issue
Dec 2, 2020
Since protobuf 3.14, the Well Known Types declare APIv2 package paths, which means generated code that imports them will import APIv2 packages. This PR is intended to be cherry-picked to the 0.23 and 0.24 release branches. It may slow down builds, since both APIv1 and APIv2 packages will be compiled; we can't tell which is needed during analysis. For #2721
jayconrod
pushed a commit
that referenced
this issue
Jun 28, 2021
Since protobuf 3.14, the Well Known Types declare APIv2 package paths, which means generated code that imports them will import APIv2 packages. Fixes #2721
bdhess
added a commit
to GoogleCloudPlatform/kms-integrations
that referenced
this issue
Aug 2, 2021
This makes it easier to test cases where the deadline is exceeded. I think I have an ever better/more flexible approach that we can move to later, but it's blocked by an open issue in rules-go: bazelbuild/rules_go#2721 Change-Id: Ie5533a39281cd48138f55a0538d1bfc676552f26
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of rules_go are you using?
v0.24.7
What version of gazelle are you using?
n/a
What version of Bazel are you using?
3.7.0
Does this issue reproduce with the latest releases of all the above?
yes
What operating system and processor architecture are you using?
Darwin amd64
What did you do?
Build pretty much any
go_proto_library
using protoc 3.14 or later.For example:
What did you expect to see?
Successful build.
What did you see instead?
Analysis
From an email with @dsnet:
The text was updated successfully, but these errors were encountered: