-
Notifications
You must be signed in to change notification settings - Fork 810
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
gogo/proto marshalling is failing with latest github.com/golang/protobuf v1.4.0-rc.4 #678
Comments
I've seen a similar issue:
|
Try rolling back golang/protobuf: |
I cannot other modules require at least protobuf v1.4.0-rc.4. |
due to https://blog.golang.org/protobuf-apiv2 version part will show some clues, try to upgrade a stable version like v1.4.0 |
look go.mod of google.golang.org/protobuf , you will get answer |
This comit fixes #4508 Gogoproto is not compatible with APIv2 protoc-gen-go. Track the issue here: gogo/protobuf#678 Meanwhile, this commit switches to google protobuf to unmarshal firebase struct. Add a missing method EmitAuditEvent causing teleport to crash with firestore events backend.
This comit fixes #4508 Gogoproto is not compatible with APIv2 protoc-gen-go. Track the issue here: gogo/protobuf#678 Meanwhile, this commit switches to google protobuf to unmarshal firebase struct. Add a missing method EmitAuditEvent causing teleport to crash with firestore events backend.
This comit fixes #4508 Gogoproto is not compatible with APIv2 protoc-gen-go. Track the issue here: gogo/protobuf#678 Meanwhile, this commit switches to google protobuf to unmarshal firebase struct. Add a missing method EmitAuditEvent causing teleport to crash with firestore events backend.
This comit fixes #4508 Gogoproto is not compatible with APIv2 protoc-gen-go. Track the issue here: gogo/protobuf#678 Meanwhile, this commit switches to google protobuf to unmarshal firebase struct. Add a missing method EmitAuditEvent causing teleport to crash with firestore events backend.
We were seeing similar issues. Our error is:
For us issues were triggering on types with custom marshalling/unmarshalling. We are able to fix the issue by using the experimental encoding.RegisterCodec method. We are currently evaluating whether this is a go forward fix for us. I am unfamiliar with the mechanics that grpc uses to choose a codec, why it worked before or why it stopped working. Perhaps this sheds some light on the problem for those who know more about this issue. Edit: We were able to make it quite far using this technique but were ultimately blocked by the following error:
Details here: |
panic: protobuf tag not enough fields in ListDeviceRequest.state:
goroutine 25 [running]:
github.com/gogo/protobuf/proto.(*unmarshalInfo).computeUnmarshalInfo(0xc000162000)
/Users/adithyas/go/pkg/mod/github.com/gogo/[email protected]/proto/table_unmarshal.go:341 +0x17fb
The text was updated successfully, but these errors were encountered: