-
-
Notifications
You must be signed in to change notification settings - Fork 668
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
Linker fails with fingerprint mismatch in google.golang.org/genproto/ #2758
Comments
This error happens when multiple packages with the same This is especially common with protos, since it's easy to mix pre-generated There have been a number of bug fixes on the rules_go 0.24.x branch, so please try upgrading to that or 0.25.x. You'll likely see better error messages there. |
Thanks for the help. When I use rules_go 0.25, I now get a different error:
Grepping through the packages downloaded by Bazel, I see that rules in the following two packages both define a library whose import path is
It looks like they are both imported by rules_go. Is there a way around it? The content of the former file is:
The latter is
|
Not sure I have a good solution at the moment. You could override one of them and provide build files that replace conflicting |
Any solution to this problem? |
In our case, (1) setting disable_global option in gazelle, (2) updating io_bazel_rules_go to 0.25.0, and (3) updating bazel_gazelle to 0.22.2 magically fixed the problem. I still don't know why. |
What version of rules_go are you using?
1.24.0
What version of gazelle are you using?
0.21.1
What version of Bazel are you using?
3.5.0
Does this issue reproduce with the latest releases of all the above?
yes
What operating system and processor architecture are you using?
Linux, Ubuntu 20.04, x64
Any other potentially useful information about your toolchain?
What did you do?
bazel build a go binary
What did you expect to see?
it should succeed.
What did you see instead?
Some of the pertinent lines in go.mod (and the matching bazel workspace rules are):
Sorry for a vague error description; the binary in question is from a fairly large non-opensource project and I wasn't able to create a simple repro. This error disappears when I remove some deps from BUILD files, but I can't quite figure out the minimal set of deps to make the problem happen.
I find it strange that secretmanager/v1beta1 is using protobuf/field_mask in the same package and fails with a fingerprint mismatch. Can someone give me some guidance as to how to investigate this problem?
The text was updated successfully, but these errors were encountered: