-
Notifications
You must be signed in to change notification settings - Fork 19
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
[BUG] Cannot build with Bzlmod #88
Comments
@srikrsna-buf @rodaine any solutions? |
@srikrsna-buf @rodaine still stuck on this |
Hey! I am not sure if it is a problem with |
@srikrsna-buf it's not a problem with |
You can replicate the solution in #27 using |
Looks like they removed those options and moved it to a directive |
even after doing that it throws the same error |
Can you share the directives you've used? |
I hit this as well and these directives seem to have worked (I'm hitting other issues on other packages like
Those are the packages we're importing so change to whichever ones you are using. |
# gazelle:prefix github.com/ride-app/driver-service
# gazelle:build_file_name BUILD.bazel
# gazelle:exclude infra
# gazelle:proto disable_global
# gazelle:go_naming_convention go_default_library |
I tried your solution but still throws some errors. Would you mind sharing the whole gazelle setup in BUILD.bazel? |
|
Description
I'm using the upcoming bzlmod support in rules_buf and I've encountered this error.
Steps to Reproduce
Environment
Possible Solution
in #27 a possible solution includes manually changing
go_repository
arguments ingo_deps.bzl
. Since bzlmod support means there's nogo_deps.bazel
file anymore where I could manually change settings I'm stuck as it seems.Additional Context
MODULE
BUILD
The text was updated successfully, but these errors were encountered: