[protobuf] Re: Error: Mesage is incomplete or invalid

2016-04-22 Thread 'Feng Xiao' via Protocol Buffers
What implementation are you using? I don't think we support perl. If you are using a third-party implementation, you probably want to contact the author or file an issue to their github site. On Friday, April 22, 2016 at 1:34:44 PM UTC-7, Alex G wrote: > > hi. > > when I am trying to decode data

Re: [protobuf] How does HasField works in Python bindings for protobuf

2016-04-22 Thread 'Jie Luo' via Protocol Buffers
If you are using proto3, HasField is not supported for primitive types. On Wed, Apr 20, 2016 at 4:13 AM, Robert Kuska wrote: > Consider following code: > > message Fly{ > uint32 dtime = 1; > } > > >>> d.ListFields()[0][0].name > 'dtime' > >>> d.ListFields()[0][0].full_name > 'Fly.dtime > >>> >

Re: [protobuf] Golang Protobuf imports "."

2016-04-22 Thread 'Feng Xiao' via Protocol Buffers
On Fri, Apr 22, 2016 at 3:47 AM, Roger Alsing wrote: > Is there some way to make the protoc generator generate correct Golang > imports? > > Im having trouble importing other proto files and generating Go code. > > If I run the compiler using > protoc --go_out=. --proto_path=path\to\my\includes f

[protobuf] Error: Mesage is incomplete or invalid

2016-04-22 Thread Alex G
hi. when I am trying to decode data : $m = VoiceProxyProtobuf::AddDataResponse->decode($m); I got : Error: Mesage is incomplete or invalid at /usr/local/share/perl5/Google/ProtocolBuffers/CodecIV64.pm line 37 or Error: Mesage is incomplete or invalid at /usr/local/share/perl5/Google/Protoco

[protobuf] How does HasField works in Python bindings for protobuf

2016-04-22 Thread Robert Kuska
Consider following code: message Fly{ uint32 dtime = 1; } >>> d.ListFields()[0][0].name 'dtime' >>> d.ListFields()[0][0].full_name 'Fly.dtime >>> >>> d.HasField('dtime') Traceback (most recent call last): File "", line 1, in File "/home/rkuska/.local/lib/python2.7/site-packages/google/pro

[protobuf] Golang Protobuf imports "."

2016-04-22 Thread Roger Alsing
Is there some way to make the protoc generator generate correct Golang imports? Im having trouble importing other proto files and generating Go code. If I run the compiler using protoc --go_out=. --proto_path=path\to\my\includes foo.proto the generated code will contain a ´import "."´ packa