#grpc

^ fixed that problem by copying / pasting the proto each time it changes to follow the recommended gradle approach to building the files and it works.

I don't like that approach, and I'm really starting to dislike gradle in general.

Short story short, I've atttempted to convert my project over to a bazel workspace, and its been a huge headache

getting kotlin support to work with grpc is the current headache.

i've cloned grpc-java to third_party, and made the necessary changes.

boom, I can build lite-proto files

however, i still cannot build lite grpc services, the expected MyAppGrpc.java class never gets generated, and i'm missing linkage to some Message(Builder?)Lite.java files

i can probably find the MessageBuilderLite library no worries, but I'm wondering why the heck MyServiceGrpc.java never gets built

any thoughts?

I'm using golang and messing around with the naming system (dns:///blaha.tld specifically). I have one project which behaves as I'd expect, but I tried introducing GRPC in a bigger project and when using naming the Dial fails with "ERROR: 2018/05/27 08:44:52 grpclb: failed to recv init response: rpc error: code = Unimplemented desc = unknown service grpc.lb.v1.LoadBalancer". The project is vendored if that m

akes any difference, while my own is not.

do I need to expicitly link something in that I managed to do by accident in my own program?

fwiw, https://github.com/dhtech/prodaccess/blob/maste... works, https://github.com/dhtech/cert-manager/blob/grp... does not (works fine without dns:/// scheme and manual address:port though)