-
-
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
Circular dependency with protobuf #4196
Comments
@linzhp I think that we've seen this before, but I don't remember what caused it. Do you have an idea? |
Can you try disabling the |
@linzhp How can I do this in a non-root module like bazelbuild/bazel-central-registry#3414? |
You can send a PR to add generally useful constraints to https://github.com/bazel-contrib/bazel-gazelle/blob/master/internal/bzlmod/default_gazelle_overrides.bzl. |
What version of rules_go are you using?
0.51.0
What version of gazelle are you using?
0.40.0
What version of Bazel are you using?
8.0
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
Linux
Any other potentially useful information about your toolchain?
I found this in https://github.com/bazelbuild/bazel-central-registry/pull/3414/files (logshttps://buildkite.com/bazel/bcr-presubmit/builds/9387#0193c668-67e2-4bf9-ad25-ac0ca0d40321) but also stumbled over this in our internal workspace for other dependencies where we use the latest version of Bazel deps (go.mod might be a little bit older).
What did you do?
Use Gazelle to build go.mod dependencies.
What did you expect to see?
Working just fine.
What did you see instead?
The text was updated successfully, but these errors were encountered: