popovicu
popovicu
Right. I've tried this before, but I get issues with cyclical dependencies. Please take a look at this pull request to see the changes I've made: https://github.com/popovicu/go-grpc-bazel-example/pull/1/commits/f215918d992b0811295da566ca628ed7349bc170 If I do...
@fmeum, can we please reopen the issue? I don't have the permission to do it. 😞
@fmeum any new thoughts in the meantime before @linzhp responds?
@fmeum Is there anyone else this can be assigned to?
Friendly ping. Should this be considered a bug and if yes, what would be the priority? I personally think that this would draw a lot of people away from using...
Just wanted to confirm that @fmeum provided the correct solution and @sluongng provided a good hint for how to make it work with `WORKSPACE` projects. For posterity, I'm using this...
Hm, this project has grown quite a bit in size and it's very Bazel-centric. Is there any set of CLI flags I can pass to get some debug info? It...
Maybe something like [this](https://github.com/popovicu/go-grpc-bazel-example/blob/main/proto/BUILD)? Only instead of the gRPC library, you can use a plain proto.
You're right @fmeum. I've just run the small repro, and I figured out where things go wrong. It's the `gazelle` directive that introduces some wrinkles. ``` go_deps.gazelle_default_attributes( # Pointers here:...
Interestingly, I don't think the issues from #3971 matter anymore with all the latest versions, so the proto disabling directive no longer seems to matter, it can be safely removed...