Skip to content

Conversation

@zecke
Copy link
Contributor

@zecke zecke commented Aug 15, 2025

This reverts commit e425d46.

Moving to @io_bazel_rules_go//proto:go_grpc_v2 is not a drop-in replacement and fails if the proto library has both messages and services defined.

Fixes #2170

What type of PR is this?

Bug fix

What package or component does this PR mostly affect?

gRPC and go_proto_compiler

What does this PR do? Why is it needed?

Moving to @io_bazel_rules_go//proto:go_grpc_v2 is not a drop-in replacement and fails if the proto library has both messages and services defined. This reverts commit e425d46.

Which issues(s) does this PR fix?

Fixes #2071

Other notes for review

This reverts commit e425d46.

Moving to @io_bazel_rules_go//proto:go_grpc_v2 is not a drop-in
replacement and fails if the proto library has both messages and
services defined.

Fixes bazel-contrib#2170
@sluongng
Copy link
Contributor

I suggest not going back to the deprecated solution. Instead, let's try getting #2085 merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

gRPC: Changing go_grpc_compiler causes link time failure due protobuf messages not being generated

2 participants