Hi All,
This is Srinivas. I am new to GRPC, I am trying to compile latest grpc
(v1.7.2) version.
It's working in X86 architecture. when i am trying to compile for ARM
architecture(cortex A9) it's not working.
Please guide me the steps. One more thing i am using protobuf 3.4.0
version. I am g
The simplest way would be to serialize your messages into bytes and then
measure the size directly, right?
On Sun, Dec 10, 2017 at 11:26 AM, Tomer Praizler
wrote:
> Couldn't find a nice and easy way to calculate my protobuf sizes using
> python. Is there a recommended way?
>
> I am sending my pr
I have a similar problem: after successfully downloading and un-taring
protobuf-all-3.5.0.tar.bz, I also successfully ran ."/confiure", "make"
and "make check". Then "sudo make install" failed with:
libtool: install: (cd /downloads/protobuf-3.5.0/src; /bin/sh
/downloads/protobuf-3.5.0/libtool
Couldn't find a nice and easy way to calculate my protobuf sizes using
python. Is there a recommended way?
I am sending my protobufs into rabbitmq, and huge messages causing my
connection to break. I want to be able to validate the size before sending
a message.
--
You received this message
a zero tag is never valid in any protobuf data, although it wouldn't be
unheard of for folks to use a zero tag as a sentinel value to demark
multiple root messages. Protoc has some facilities to check the insides of
a message that might help you figure out how likely it is to be a match,
but it won
Hey Jeroen!
Dis you get any method to check if a .pb file is generated from givem
.proto file? Actually, I'm getting error while deserializing a .pb file,
"The protocol message contained invalid tag(zero)." I was wondering if the
two files are compatible.
Thanks in advance.
On Saturday, Novem
Thanks, I think I understand now. I do think identifying a "root" type in
the .proto would have been a big help and wouldn't have cost much space or
bandwidth.
If I had time, I'd write a tool that would infer the root by testing for
types that have matching fields, but life is short...
On Sun
On Sun, Dec 10, 2017 at 11:23 AM, Jim Baldwin wrote:
> Perhaps it might help if I understood the output of protoc --decode_raw.
>
> Here's an example of a .caffemodel file I'm trying to inspect. Is there a
> description of what the numbers mean in this file?
As I said... it's a sequence of (tag,
Hmmm. Back to the core problem. I am not certain I have the root.
Case in point:
caffe.proto:
https://github.com/BVLC/caffe/blob/master/src/caffe/proto/caffe.proto
I'm gradually thinking the root of this file is "NetParameter", but I'm not
sure how I was supposed to know that. :-P
I still
oh, there is a root. if i had to guess it has something like:
message TheRootMessageType {
required string name = 1;
repeated SomeNoun items = 100;
}
On 10 Dec 2017 4:42 p.m., "Jim Baldwin" wrote:
> In this case, it looks like there isn’t a root. Rather, this format is a
> series of
In this case, it looks like there isn’t a root. Rather, this format is a
series of top-level parameters. So, I have to give it the Parameter I’m
looking for. The problem I have with this is the order of parameters _might_
matter, and I lose that by only looking for one.
On Dec 10, 2017, at 8
as I ubderstand it, --decode *will do that*. it doesn't decode *just* the
root : but, it needs to know the root message type in order to correctly
interpret the data
On 10 Dec 2017 4:32 p.m., "Jim Baldwin" wrote:
> OK, this helps. I need to figure out what the "root" message is. It
> seems lik
OK, this helps. I need to figure out what the "root" message is. It seems
like an omission in the whole PB thing that you can't specify the .proto
and do a --decode_everything.
On Sunday, December 10, 2017 at 8:23:12 AM UTC-8, Marc Gravell wrote:
>
> You can and it does. The problem is that th
They are field numbers. They don't mean anything by themselves other than
to identify each field. If you want to know the logical *name* of each
field, you need the .proto schema.
On 10 Dec 2017 4:23 p.m., "Jim Baldwin" wrote:
> Perhaps it might help if I understood the output of protoc --decode
Perhaps it might help if I understood the output of protoc --decode_raw.
Here's an example of a .caffemodel file I'm trying to inspect. Is there a
description of what the numbers mean in this file?
1: "VGG_ILSVRC_16_layers"
100 {
1: "input-data"
2: "Python"
4: "data"
4: "im_info"
4:
You can and it does. The problem is that the wire format by itself doesn't
tell it **what message type** the root object is. So you need to tell it in
the additional parameter to --decode
On 10 Dec 2017 3:14 p.m., "Jim Baldwin" wrote:
It's not really just a sequence; it's a hierarchy, isn't it?
It's not really just a sequence; it's a hierarchy, isn't it? Why can't I
use --decode or something like that?
On Saturday, December 9, 2017 at 4:20:15 PM UTC-8, Ilia Mirkin wrote:
>
> On Sat, Dec 9, 2017 at 5:52 PM, Jim Baldwin > wrote:
> > I have a protobuf file, and a .proto file that desc
17 matches
Mail list logo
