Done myself: test.proto enum MyEnum { Default = 0; Variant1 = 1; Variant100 = 100; } message Test { required string f1 = 1; required int64 f2 = 2; repeated uint64 fa = 3; repeated int32 fb = 4; repeated int32 fc = 5 [packed = true]; repeated Pair pairs = 6; optional bytes bbbb … Read more
There are many ways to approach the problem of saving a model in TensorFlow, which can make it a bit confusing. Taking each of your sub-questions in turn: The checkpoint files (produced e.g. by calling saver.save() on a tf.train.Saver object) contain only the weights, and any other variables defined in the same program. To use … Read more
There is Timestamp message type since protobuf 3.0, that’s how to create it in model: syntax = “proto3”; import “google/protobuf/timestamp.proto”; message MyMessage { google.protobuf.Timestamp my_field = 1; } timestamp.proto file contains examples of Timestamp using, including related to Linux and Windows programs. Example 1: Compute Timestamp from POSIX time(). Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: … Read more
As per the documentation, you aren’t able to directly assign to a repeated field. In this case, you can call extend to add all of the elements in the list to the field. person.id.extend([1, 32, 43432])
There are some issues with building protobuf 2.4.1 from source on a Mac. There is a patch that also has to be applied. All this is contained within the homebrew protobuf241 formula, so I would advise using it. To install protocol buffer version 2.4.1 type the following into a terminal: brew tap homebrew/versions brew install … Read more
ASN.1 is an ISO/ISE standard. It has a very readable source language and a variety of back-ends, both binary and human-readable. Being an international standard (and an old one at that!) the source language is a bit kitchen-sinkish (in about the same way that the Atlantic Ocean is a bit wet) but it is extremely … Read more
I wrote a detailed comparison of a few serialization systems, including Protobufs and FlatBuffers, here: https://kentonv.github.io/capnproto/news/2014-06-17-capnproto-flatbuffers-sbe.html However, the comparison focuses more on comparing the three new “zero-copy” serialization systems, and includes Protobufs mostly as a reference point. Also, I’m the author of Cap’n Proto, and also the author of Protobufs v2 (I was responsible for … Read more
Protocol buffers is (are?) an Interface Definition Language and serialization library: You define your data structures in its IDL i.e. describe the data objects you want to use It provides routines to translate your data objects to and from binary, e.g. for writing/reading data from disk gRPC uses the same IDL but adds syntax “rpc” … Read more
Since protobuf release 3.15, proto3 supports using the optional keyword (just as in proto2) to give a scalar field presence information. syntax = “proto3”; message Foo { int32 bar = 1; optional int32 baz = 2; } A has_baz()/hasBaz() method is generated for the optional field above, just as it was in proto2. Under the … Read more
Kenton’s comment below is sound advice: … we as developers are really bad at guessing what we might want in the future. So I recommend being safe by always defining custom params and results types for every method, even if they are empty. Answering my own question: Looking through the default proto files, I came … Read more