GenProto | online GUI tool used to visualize prototxt | Machine Learning library

The gist of this error is that the version of binary used to generate the code isn't compatible with the current version of code. A quick and easy solution would be to try updating the protoc-gen-go compiler and the gRPC library to the latest version.

go get -u github.com/golang/protobuf/protoc-gen-go

then regen the proto

heres a link to a reddit thread that discusses the issue

It's good that you started GRPC.

It seems like you're protoc-gen-go is old and needed to be updated,

to update it you should

• first, remove the current one, to find where it stored, you can use the echo $PATH command to find out where this file is. then remove it.

• second, install the new one, for installing it you can run this command.

  go install google.golang.org/grpc/cmd/protoc-gen-go-grpc

  Note If you have any problem to get it, use this command instead,

  go get -u github.com/golang/protobuf/protoc-gen-go

after the update, you must edit your go.mod file.

change this line:

The Issue is solved by this comment.

Localhost in the container is not the same as where the server is running. – Matt 14 mins ago

I fixed the api/main.go.

The json Encoder ist not 100% compatible with protobuf.

Use protojson.Marshal from "google.golang.org/protobuf/encoding/protojson" instead.

See this Playground.

It is not as fast though.

EDIT To answer the request for a faster alternative:

One could utilise a custom error struct that holds all required data & unwrap the grpc status & its details manually. See this playground. On my machine this saved about 15% time.

If your git package has tag version, you can use this command:

I've found a solution!

I need to use the jsonpb marshaler and return it as string with Gin

Here an example:

Its a bug with version inconsistency between go-micro and grpc. About a week ago I tried to follow the tutorial which you mention and got same error. If you want to fix the error above please follow the interactions below the link: https://github.com/etcd-io/etcd/issues/11563.

In additionally I recommend you just build grpc service without go-micro, due to version inconsistency.

I've been having the same issue for the past couple of days and figured it out. The library I was using to create the API client and create a task was using different credentials than I expected.

For those that are using "application default credentials", or at least letting the client find credentials automatically, take a look at this page: https://cloud.google.com/docs/authentication/production#finding_credentials_automatically

I had created a service account with all the right roles and was assuming the API client was using the service account. Turns out I wasn't passing in the key file and thus it was using the "application default credentials". For my use case, "application default credentials" referred to the App Engine default service account. When I supplied the API client with a key file for my custom service account, it worked.

You need to manually convert the []*User slice to []*genproto.User one. Golang can't let you do the cast