[protobuf] Error extracting protoc for version 3.11.4: Unsupported platform: protoc-3.11.4-osx-aarch_64.exe

-3.11.4-osx-aarch_64.exe -> [Help 1] any help or support to fix this issue is appreciated regards, Ravi Leeladhar -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails fro

[protobuf] Looking for daily build binaries for protobuf

Hi all, Can any please tell where I can find the daily build's protobuf binary? Regards, Ravi Salamani -- 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, se

Re: [protobuf] toolchain for protobuff

re > <https://github.com/protocolbuffers/protobuf/tree/master/kokoro/release/protoc> > > to build protoc binaries. > > On Tue, Aug 13, 2019 at 2:23 AM Ravi Salamani > wrote: > >> I need information on which toolchain is used for generating protobuff >> binaries?

[protobuf] cross compilation of protobuf for multiarch

I need information on how protobuf binaries are generated for multiple Arch? Which docker image is used for building non x86 binaries? Regards, Ravi S -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this

[protobuf] toolchain for protobuff

I need information on which toolchain is used for generating protobuff binaries? Which docker image is used for building non x86 binaries? Regards, Ravi S -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from

[protobuf] Re: How to speedup serialization and deserialization process?

Marc, Thank you very much for the detailed explanation. I got it. Due to curiosity, I tried manual explicit serialization. I needed to code more but indeed it worked way faster as you suggested. Thanks again for the wonderful explanation. - Ravi On Wednesday, December 20, 2017 at 10:00:31

[protobuf] Re: How to speedup serialization and deserialization process?

Any suggestions, please? On Wednesday, December 20, 2017 at 10:00:31 PM UTC+9, Ravi wrote: > > I have defined the Protocol Buffers message file as follows: > > syntax = "proto3"; > package Tutorial; > import "google/protobuf/timestamp.proto"; > option c

[protobuf] How to speedup serialization and deserialization process?

for information, the length of the byte array is roughly 3,784,000. *I want to know how to speed up serialization and deserialization process?* - Thanks Ravi -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe

Re: [protobuf] protoc generator : The code of constructor ... is exceeding the 65535 bytes limit

Thanks for the solution. Extensions seems good for our usecase. On Thursday, 8 January 2015 19:07:07 UTC, Henner Zeller wrote: > > On 5 January 2015 at 05:09, ravi kiran tunuguntla > wrote: > > protoc generated code could not be compiled. (as the constructor code > has

[protobuf] The code of constructor GenericDataRow(CodedInputStream, ExtensionRegistryLite) is exceeding the 65535 bytes limit

I have a message which has about 1000 attributes. protoc generated code could not be compiled (The code of constructor GenericDataRow(CodedInputStream, ExtensionRegistryLite) is exceeding the 65535 bytes limit). We need the ability to merge attributes in messages, and hence the definition has

[protobuf] protoc generator : The code of constructor ... is exceeding the 65535 bytes limit

protoc generated code could not be compiled. (as the constructor code has exceeded 65535 bytes limit). What can be done to work around this? -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving e

[protobuf] Re: How to use protoc --decode option?

arameter, protoc will treat that file as a ".proto" file. You should pipe > the payload to protoc instead. > > On Tue, Jul 5, 2011 at 7:30 PM, Ravi wrote: > > Hi, > > > I am trying to convert a protobuf stream in to a readable format. I > > got following excep

[protobuf] How to use protoc --decode option?

Hi, I am trying to convert a protobuf stream in to a readable format. I got following exception. protobuf.txt:2:1: Invalid control characters encountered in text. protobuf.txt:2:2: Expected top-level statement (e.g. "message"). protobuf.txt:2:9: Invalid control characters encountered in text. S

[protobuf] Re: How to Programmatically determine the Builder method names (getter and setter) for a given field name

>     if (value == null) { >       builder.clearField(fieldDescriptor); >     } else { >       builder.setField(fieldDescriptor, value); >     } >   } > * > * > > On Tue, Mar 15, 2011 at 2:19 AM, Ravi wrote: > > Hi, > > > We would like to know how to det

[protobuf] How to Programmatically determine the Builder method names (getter and setter) for a given field name

Hi, We would like to know how to determine the getter and setter method names generated in java builder class for a particular field defined in proto message. Of course, the simple rule says that * Convert first letter of the field name to upper case * prefix "get" or "set" to the field name But

[protobuf] Specifications of java data accessor classes that gets generated from proto files.

e any defined set of rules/specifications that this is how the generated data accessor class will look like then we can think of writing a tool which generates the classes directly from xsd. Any help/suggestion would be appreciated. Thanks, Ravi -- You received this message because you are subs