You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to deserialize Protobuf messages that use the Any type, and uses some of the wrapper types for compatibility with primitive types. Particularly those found here. Here is a minimal example that demonstrates the issue I am running into. The following works:
ERRO Error: failed to unmarshal JSON message 'PersonBroken': proto: (line 1:20): unable to resolve "type.googleapis.com/google.protobuf.BoolValue": "not found" @service=benthos label="" path=root.pipeline.processors.2.catch.0
If I remove the BoolValue field, I get the same error with the StringValue field instead. It seems to be related to this issue: golang/protobuf#1156 but I tried adding
Hey @Zambito1 I think you'll have to configure import_paths and add in there the path to wherever you install protoc on your platform (guess the platform doesn't really matter much in this case, since you only need the .proto files). You can get the latest release here: https://github.com/protocolbuffers/protobuf/releases/latest. It should contain an include folder which has the files you need.
PS: Converting to a discussion as mentioned in #2026.
I am trying to deserialize Protobuf messages that use the Any type, and uses some of the wrapper types for compatibility with primitive types. Particularly those found here. Here is a minimal example that demonstrates the issue I am running into. The following works:
person.proto
:config.yaml
:(worth noting that the round trip maps
false
tonull
, but that is not the issue I am trying to cover here)But this does not:
config.yaml
:It fails with the following log:
If I remove the
BoolValue
field, I get the same error with theStringValue
field instead. It seems to be related to this issue: golang/protobuf#1156 but I tried addingxor
to
internal/impl/protobuf/processor_protobuf.go
, and neither worked.The text was updated successfully, but these errors were encountered: