-
Notifications
You must be signed in to change notification settings - Fork 213
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
Temporal Go SDK can not be used with bazel_gazelle 0.32+ #1331
Comments
I am not super familiar with bazel, but is the problem really with |
Slightly different problem with Bzlmod, but also traces back to
Hopefully will be fixed by #1365 |
@SpencerC I am not sure how your PR is related to this issue. Note: |
@Quinn-With-Two-Ns oops, got my gRPC packages mixed up! It works on HEAD. @saumitrabhave try |
Thanks @Quinn-With-Two-Ns and @SpencerC ... let me check and get back |
Closing since the Go SDK now uses |
Expected Behavior
The prject should build fine
Actual Behavior
Error is produced is bazel build like
/external/com_github_grpc_ecosystem_grpc_gateway/runtime/BUILD.bazel:5:11: no such package '@go_googleapis//google/api': The repository '@go_googleapis' could not be resolved: Repository '@go_googleapis' is not defined and referenced by '@com_github_grpc_ecosystem_grpc_gateway//runtime:go_default_library'
Steps to Reproduce the Problem
Specifications
Errors:
Works Fine with
Additional Details
I am a noob in bazel and go build tool chains in general but with whatever I could see there might be multiple issues at play. even to build with older versions(as mentioned above) I had to add
build_naming_convention = "go_default_library", #keep
to thecom_github_grpc_ecosystem_grpc_gateway
dependency.Even after adding this, if I increase the bazelle_gazelle version, it still errors out with error above. I think it has something to do with the fact that bazelle_gazelle stopped resolving go and proto imports to @go_googleapis since 0.32 as per https://github.com/bazelbuild/bazel-gazelle/releases. and that is where the injection point is for the error I am facing.
The text was updated successfully, but these errors were encountered: