[protobuf] protobuf::Any Message vs MessageLite interface
Hi, I was wondering if there is any reason that Any type is implemented in terms of Message interface rather than MessageLite? It'd seem to me that all this class needs to work correctly is to use GetTypeName() on MessageLite interface. My motivation is, of course, to be able to use Any type with Lite run time. --Arpit -- 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 https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
Re: [protobuf] Re: Application doesn't load on a very small number of (Windows) systems
We now also know that this only happens on Windows 2003 x86 machines which have a Pentium 3 processor. My first attempt to provide an executable with optimization and SSE2 support disabled have been unsuccessful. At this point I don't think it's something that's related to Protocol Buffers, it just seems to generate code that's not fully compatible with that processor architecture. On Tuesday, October 4, 2016 at 12:37:24 PM UTC-5, Adam Cozzette wrote: > > It sounds like the static descriptor data is somehow getting corrupted. On > the affected systems does it happen reproducibly every time the application > starts up? > > On Mon, Oct 3, 2016 at 10:54 AM, Ingmar Koecher> wrote: > >> I can now also confirm that this problem only occurs on Windows Server >> 2003 x86 hosts. >> >> >> On Monday, October 3, 2016 at 8:48:48 AM UTC-5, Ingmar Koecher wrote: >>> >>> We've been using protocol buffers for a couple of months (version 2, >>> exclusively on Windows) and while it works on 99.9% of systems, on a few >>> systems an application won't start with the following errors: >>> >>> [libprotobuf ERROR google\protobuf\descriptor_database.cc:315] >>> Invalid file descriptor data passed to EncodedDescriptorDatabase::Add(). >>> >>> [libprotobuf FATAL >>> google\protocol_buffers\src\google\protobuf\descriptor.cc:1018] >>> CHECK failed: >>> generated_database_->Add(encoded_file_descriptor, size): >>> >>> Unfortunately I don't have access to those systems, so I can't debug it. >>> I've tried to send special instrumented versions to capture the output, but >>> I haven't been able to figure out what the issue is. >>> >>> I have a suspicion that it only affects Windows 2003 Servers, but I'm >>> not sure. The protocol buffers are statically linked from Visual Studio >>> 2010. >>> >>> Do these error messages ring a bell with anyone? >>> >>> >>> Thanks! >>> >> -- >> 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+u...@googlegroups.com . >> To post to this group, send email to prot...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/protobuf. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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 https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
Re: [protobuf] Re: Application doesn't load on a very small number of (Windows) systems
It sounds like the static descriptor data is somehow getting corrupted. On the affected systems does it happen reproducibly every time the application starts up? On Mon, Oct 3, 2016 at 10:54 AM, Ingmar Koecherwrote: > I can now also confirm that this problem only occurs on Windows Server > 2003 x86 hosts. > > > On Monday, October 3, 2016 at 8:48:48 AM UTC-5, Ingmar Koecher wrote: >> >> We've been using protocol buffers for a couple of months (version 2, >> exclusively on Windows) and while it works on 99.9% of systems, on a few >> systems an application won't start with the following errors: >> >> [libprotobuf ERROR google\protobuf\descriptor_database.cc:315] >> Invalid file descriptor data passed to EncodedDescriptorDatabase::Add(). >> >> [libprotobuf FATAL google\protocol_buffers\src\go >> ogle\protobuf\descriptor.cc:1018] CHECK failed: >> generated_database_->Add(encoded_file_descriptor, size): >> >> Unfortunately I don't have access to those systems, so I can't debug it. >> I've tried to send special instrumented versions to capture the output, but >> I haven't been able to figure out what the issue is. >> >> I have a suspicion that it only affects Windows 2003 Servers, but I'm not >> sure. The protocol buffers are statically linked from Visual Studio 2010. >> >> Do these error messages ring a bell with anyone? >> >> >> Thanks! >> > -- > 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 https://groups.google.com/group/protobuf. > For more options, visit https://groups.google.com/d/optout. > -- 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 https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
[protobuf] Is there a way to encode nested arrays as one object/message within protobuf?
Suppose in some json formatted schema I have "foo": [[12, 34],[56,78]]. I know I could do message foo_sub{ repeated int value = 1; } message Document{ repeated foo_sub foo = 1; } But if I directly convert this into json, it will be: "foo":[{"value":[12, 34]}, {"value":[56,78]}] While, in terms of information, these are equivalent, using the protobuf3 json conversion function, it doesn't produce quite the same json as the initial kind. Is there a way to do this kind of functionality? To an arbitrary depth of arrays? Suppose I write a custom protobuf to json string function, instead of relying on the included one. Suppose that this 'foo' field is a message in a larger protobuf that gets translated into a json string. Is there a way to tell that larger protobuf to use the custom function I made for its sub-message? -- 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 https://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.