Strange error "incorrect wire type for tag: 5"

Question

Strange error "incorrect wire type for tag: 5"

midev opened this issue 14 years ago · 6 comments

Hello,

I receive the error "incorrect wire type for tag: 5" when compiling the following message with ruby-protoc. But I don't have this error with the original google compiler:

package MyPackage; 
message MyDate
{
    required uint32 abcde = 1;
}

What is strange is that if I change the field's name from 'abcde' to 'abcd' for example, the message compiles successfully. More generally it looks like the error appears when the field's name is 5 characters long... did I miss something ? thanks !

Marc-André

Answer 1 · 2010-12-14T15:25:41.000Z

Can you paste here the exact command line you used to compile this .proto file, and also the output of running protoc --version ? I am able to compile this successfully with ruby-protocol-buffers so I'll need more info to track down what's different in your environment.

Also, what operating system and ruby version are you using?

Answer 2 · 2010-12-15T07:05:39.000Z

Windows XP Pro SP3
ruby 1.9.1p430
libprotoc 2.3.0
ruby-protocol-buffers 0.8.4

command line is:
ruby-protoc test.proto
C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/decoder.rb:18:in decode': incorrect wire type for tag: 5 (ProtocolBuffers::DecodeError) from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/message.rb:290:inparse'
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/message.rb:296:in parse' from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/field.rb:545:indeserialize'
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/decoder.rb:41:in decode' from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/message.rb:290:inparse'
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/message.rb:296:in parse' from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/field.rb:545:indeserialize'
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/decoder.rb:41:in decode' from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/message.rb:290:inparse'
from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/lib/protocol_buffers/runtime/message.rb:296:in parse' from C:/Ruby191/lib/ruby/gems/1.9.1/gems/ruby-protocol-buffers-0.8.4/bin/ruby-protoc:37:in<top (required)>'
from C:/Ruby191/bin/ruby-protoc:19:in load' from C:/Ruby191/bin/ruby-protoc:19:in

'

Answer 3 · 2010-12-15T07:14:53.000Z

sorry I closed the issue by accident..

Answer 4 · 2010-12-15T15:22:46.000Z

As stated in the Readme, ruby-protocol-buffers is completely untested in Windows. I'd love to support Windows better in the library, I just don't have easy access to a Windows box for testing. I'll try to track one down and figure out why this is failing on Windows. Ruby 1.9.1 and 1.9.2 are supported, so I think it's got to be Windows related.

Answer 5 · 2010-12-19T19:53:15.000Z

I've tracked down the issue, the ruby Tempfile class doesn't open files in "binary mode" by default, which screws things up on windows

Answer 6 · 2010-12-19T19:54:42.000Z

write to temporary files in binmode for windows compatibility, closed by 0428bd2