Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 633 by stijnsan...@gmail.com: Double encoded as length-delimited wire-type
http://code.google.com/p/protobuf/issues/detail?id=633

What steps will reproduce the problem?
1. Using https://github.com/rethinkdb/rethinkdb/blob/next/src/rdb_protocol/ql2.proto
2. Using a Datum with r_num=1.0
3. Serializing to binary for network transport

What is the expected output?
somewhere in the binary data:
0x19 and 8 bytes for the double r_num

What do you see instead?
0x1A and 8 bytes, typically the first one being 0x00 throwing off readers that depend on the 3-bit wire-type-indicator.

See also

https://github.com/rethinkdb/rethinkdb/issues/2286

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--
You received this message because you are subscribed to the Google Groups "Protocol 
Buffers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to protobuf+unsubscr...@googlegroups.com.
To post to this group, send email to protobuf@googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

Reply via email to