Comment #20 on issue 66 by spaans: cannot install using easy_install
http://code.google.com/p/protobuf/issues/detail?id=66
you could release a 2.3.1 specifically to fix this issue - I've had to add
a 2.5 and
a 2.6 egg to our svn tree to prevent buildout from fetching the (wrong)
zipfile
I tried to use protocol buffer in hadoop,
so far it works fine with SequenceFile, after I hook it up with a simple
wrapper,
but after I put in a compressor in sequenceFile, it fails, because it read
all the messages and yet still wants to advance the read pointer, and
then readTag() returns 0,
We have a core dump here:
#0 0xf749b0d9 in std::string::size () from /usr/lib/libstdc++.so.6
#1 0x0822119c in bd::Header::ByteSize ()
#2 0x082323b3 in
google::protobuf::internal::WireFormat::MessageSizeNoVirtualbd::Header ()
#3 0x082257cd in bd::Request::ByteSize ()
#4 0x08233773 in
Hi All.
I am trying to detect when I receive a protocol buffer that is not of
the expected type. For example.
void myMethod(byte[] theData)
{
TheMsgTypeExpected theMsg = TheMsgTypeExpected.parseFrom(data);
}
Now, if I pass in a byte[] of a protocol buffer that is of a type that
I do not
Just need to add my 10c worth, seeing that my name was mentioned :-)
Final fields are considered immutable by the JMM. The fact that you
CAN change them does not matter to that definition. Final fields are
allowed to be inlined at runtime, which means that changing them might
cause visibility
I am confused on how to detect this scenario, and ultimately prevent
such things occurring.
You can't, at least in the simple way. Protocol buffers on the wire
have no type information associated with them, and they're explicitly
designed so that they can accept fields they don't expect to be
Comment #6 on issue 165 by ken...@google.com: can not link for mips
architecture
http://code.google.com/p/protobuf/issues/detail?id=165
As I said before, after running configure, just edit config.h (in the root
directory
of the package) and change the hash-related parts to use hash_map
Please reply-all so the mailing list stays CC'd. I don't know anything
about the libraries you are using so I can't really help you further. Maybe
someone else can.
On Thu, Feb 18, 2010 at 12:46 PM, Yang tedd...@gmail.com wrote:
thanks Kenton,
I thought about the same,
what I did was
On Wed, Feb 17, 2010 at 12:19 AM, Romain Francois
romain.francois.r.enthusi...@gmail.com wrote:
On 02/17/2010 12:51 AM, Kenton Varda wrote:
The Reflection interface already provides a way -- FieldSize() and
GetRepeatedX(). The only problem is that it's a bit slower than the
generated
