-
-
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
Dependency cycle after go_proto_reset_plugin_ #3906
Comments
This is fixed by bazel-contrib/bazel-gazelle@b3cddc0, which will be part of the next release. You can also apply the directive manually with a |
I upgraded to bazel-gazelle 0.36.0 (includes the linked PR) and hit a different cycle:
The commonality looks like |
@jschaf Is this also fixed by adding a |
Yes, I'm using a workspaces rather than bzlmod, so the following worked for me:
|
This broke our CI with
|
What version of rules_go are you using?
0.46.0. I'm using bzlmod too, btw.
What version of gazelle are you using?
0.35.0
What version of Bazel are you using?
7.0.2
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
MacOS - M2
Any other potentially useful information about your toolchain?
I'm trying to incorporate a golang app in my monorepo build for the first time. I have no toolchain customizations in place.
What did you do?
Attempting to compile a minimal app (terraform provider) produces a dependency cycle:
Some relevant portions of my files:
Excerpt from
MODULE.bazel
:go.mod
:What did you expect to see?
Project compiles, or a helpful error message.
What did you see instead?
Error message regarding cycle. The source of the cycle appears to be
@@rules_go~0.46.0//proto:go_proto_reset_plugin_
, but this appears to be generated by rules go. Further guidance on debugging would be helpful.The text was updated successfully, but these errors were encountered: