protobuf | 24 Feb 13:34 2015

Issue 691 in protobuf: Make procedure not able to finish on Ubuntu 14.10

Status: New
Owner: liujisi <at> google.com
Labels: Type-Defect Priority-Medium

New issue 691 by kr... <at> 163.com: Make procedure not able to finish on Ubuntu  
14.10
https://code.google.com/p/protobuf/issues/detail?id=691

What steps will reproduce the problem?
1.downlaod protobuf-2.5.0.tar.gz
2.use tar -xzf protobuf-2.5.0.tar.gz to extract all files
3.use ./configure to do the configuration
4.run command make

What is the expected output? What do you see instead?
The make process should have ended, but it run and run without stopping.

What version of the product are you using? On what operating system?
version: protobuf-2.5.0.tar.gz
operating system: Ubuntu 14.10 64bit

Please provide any additional information below.

I attached a log file as a output by using the command make &> Error.txt
Such log come out repeatedly:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -pthread -Wall  
-Wwrite-strings -Woverloaded-virtual -Wno-sign-compare -O2 -g -DNDEBUG -MT  
cpp_message_field.lo -MD -MP -MF .deps/cpp_message_field.Tpo -c  
google/protobuf/compiler/cpp/cpp_message_field.cc -o cpp_message_field.o  
(Continue reading)

protobuf | 23 Feb 19:29 2015

Re: Issue 119 in protobuf: TYPE_BOOL collides with MacOS macro


Comment #12 on issue 119 by tam... <at> gmail.com: TYPE_BOOL collides with MacOS  
macro
https://code.google.com/p/protobuf/issues/detail?id=119

crosslinking https://github.com/google/protobuf/issues/140

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

-- 
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

protobuf | 21 Feb 13:09 2015

Re: Issue 119 in protobuf: TYPE_BOOL collides with MacOS macro


Comment #11 on issue 119 by daen... <at> gmail.com: TYPE_BOOL collides with  
MacOS macro
https://code.google.com/p/protobuf/issues/detail?id=119

Is this bug just abandoned? It's still broken.

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

-- 
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

protobuf | 21 Feb 01:30 2015

Issue 690 in protobuf: protoc can produce cpp code that fails to compile due to naming clash on generated classes

Status: New
Owner: liujisi <at> google.com
Labels: Type-Defect Priority-Medium

New issue 690 by btkenn... <at> gmail.com: protoc can produce cpp code that  
fails to compile due to naming clash on generated classes
https://code.google.com/p/protobuf/issues/detail?id=690

What steps will reproduce the problem?
1. download / build protobuf 2.6.1
2. cd to src dir, run protoc to generate cpp code for testcase.proto  
(./protoc --cpp_out=. testcase.proto)
3. compile with g++ (g++ -I. -c testcase.pb.cc)
4. see errors due to naming clash

What is the expected output? What do you see instead?
I'd expect protoc to fail with a sensible error rather than having GCC  
produce a large amount of relatively incomprehensible error messages.

What version of the product are you using? On what operating system?
Using protobuf-2.6.1 built on ubuntu 12.04 with gcc 4.6

Attachments:
	testcase.proto  93 bytes

--

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
(Continue reading)

protobuf | 20 Feb 06:18 2015

Re: Issue 493 in protobuf: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented


Comment #22 on issue 493 by sjl... <at> gmail.com: protobuf-java (2.5.0)  
GeneratedMessage#getUnknownFields() not implemented
https://code.google.com/p/protobuf/issues/detail?id=493

We do see one other issue regarding the compatibility between 2.4.1 and  
2.5: TextFormat.print***() methods changed from taking Message as an  
argument to MessageOrBuilder. This causes a NoSuchMethodError when the  
versions are mismatched.

We had to patch it by overloading and adding back the old methods on top of  
2.5.

FWIW, this is one of the most frequent (and most painful) user code issues  
we encounter with Hadoop 2.

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

-- 
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

(Continue reading)

protobuf | 20 Feb 05:29 2015

Re: Issue 493 in protobuf: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented


Comment #21 on issue 493 by verun.ka... <at> gmail.com: protobuf-java (2.5.0)  
GeneratedMessage#getUnknownFields() not implemented
https://code.google.com/p/protobuf/issues/detail?id=493

Sorry to re-surrect this, but we've run into this exact same issue when  
trying to move to the CDH5 distribution of Hadoop, which is using Protobuf  
2.5.0, while our code base is still using Protobuf 2.4.1.

I'd like to find out if the submitted patch is complete or if there are  
others places where patches need be applied...

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

-- 
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

protobuf | 18 Feb 04:12 2015

Issue 689 in protobuf: Repeated fields do not serialize the 'size' into the file. Hence deserialize of repeated expects an unending sequence of repeated fields

Status: New
Owner: liujisi <at> google.com
Labels: Type-Defect Priority-Medium

New issue 689 by narayan.... <at> gmail.com: Repeated fields do not serialize  
the 'size' into the file. Hence deserialize of repeated expects an unending  
sequence of repeated fields
https://code.google.com/p/protobuf/issues/detail?id=689

What steps will reproduce the problem?
1. Create a MyStudent.proto with below contents
    -----------------------------------------------
   1 option optimize_for=SPEED;
   2
   3 package My;
   4
   5 message Course {
   6     required string courseName = 1;
   7     required int32 courseMarks = 2;
   8 };
   9
  10 message Student {
  11     required string rollNo      = 1;
  12     required string studentName = 2;
  13     repeated Course Courses     = 3;
  14 };
  15
  16 enum RequestType {
  17     ReadStudentRequest_e   = 0;
  18     WriteStudentRequest_e  = 1;
(Continue reading)

protobuf | 12 Feb 15:37 2015

Re: Issue 119 in protobuf: TYPE_BOOL collides with MacOS macro


Comment #10 on issue 119 by l0gicsub... <at> gmail.com: TYPE_BOOL collides with  
MacOS macro
https://code.google.com/p/protobuf/issues/detail?id=119

Will this issue be fixed somewhen? It's really disappointing.

-- 
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

--

-- 
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

Kenneth Miller | 11 Feb 21:27 2015
Picon

Serially Encode Objects into common destination

So, I have a unit test where I'm trying to ensure that encoding and decoding is sound. Basically, I kind of want to be able to serialize multiple different C++ objects into a string, and then write that string into a file. This is what I have so far:

Here's my .proto file:

message Register {
    required string regname = 1;
    required uint64 regvalue = 2;
}

message RegisterContext {
    repeated Register elem = 1;
}

message MemoryRegion {
    repeated bytes elem = 1;
}

message Image {
    required string imgName = 1;
    required MemoryRegion Memory = 2;
    required uint64 MemStart = 3;
    required uint64 MemEnd = 4;
    required bool isMain = 5;
}

message MemoryRegions {
    repeated Image elem = 1;
}

message MemoryDump {
    required RegisterContext context = 1;
    required MemoryRegions state = 2;
}


And I have language vernacular style representation objects that help me use them as I would normally.
 
//name, value
using reg=std::tuple<std::string, uint64_t>;
using reg_context=std::list<reg >;
using mem_region=std::string;
//name, memory, start, end, ismain
using image=std::tuple<std::string, mem_region, uint64_t, uint64_t, bool>;
using mem_region_set=std::list<image >;
using memory_dump=std::tuple<reg_context, mem_region_set>;



TEST(SerializationTests, test_contiguous_memory_differentiated) {
  mem_region region
="\x25\x26\x27";
  image i1
{std::make_tuple(std::string("img1"), region, 0, 1, false)},
    i2
{std::make_tuple(std::string("img2"), region+"\x28", 0, 1, false)},
      i3
{std::make_tuple(std::string("img3"), region+"\x29", 0, 1, false)};
  mem_region_set regions1
{i1, i2, i3}, regions2{i1, i3};
 
auto serialized_regions1=serialize_memory_regions(regions1);
 
auto serialized_regions2=serialize_memory_regions(regions2);
  std
::stringstream ss;
  ss
<< *serialized_regions1 << *serialized_regions2;
 
auto concatenated=ss.str();
 
auto deserialized_region1=unpack_memory_regions(concatenated);
  ASSERT_EQ
(deserialized_region1, regions1);
 
auto deserialized_region2=unpack_memory_regions(concatenated);
  ASSERT_EQ
(deserialized_region2, regions2);
}

How do I serialize multiple objects so that, whether I put them into a string stream or a ofstream, they come back out as being distict? The test that I run here results in deserialized_region1/2 each having 5 total images, merely i1, i2, i3, i1, i3

--
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Himanshu Agarwal | 11 Feb 18:53 2015
Picon

FileDescriptor to .proto?


Hi

I'm looking for a method to print a FileDescriptor to a .proto file in C++. I was browsing through the threads and code and the only solution i was able to find out is through DebugString() Api.

However i was going through code of DebugString() Api in Descriptor.cc and it appeared that the api doesn't print comments. Is there any other way to print the .proto file with all the information present in FileDescriptor?

Thank you

Himanshu Agarwal

--
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.
Burak Emre Kabakc─▒ | 7 Feb 17:39 2015
Picon

How to compile protocol buffers schema at runtime in Java?

I can create the schema (Descriptors.Descriptor) at runtime dynamically using FileDescriptorProto, also I'm able to serialize and deserialize messages using DynamicMessage.

However performance of DynamicMessage is not good enough because of the way it constructs the messages. I wonder whether it's possible to compile the schema at runtime and use it when de-serializing messages for better performance.

If protocol buffers doesn't provide a way to compile the schemas at runtime then is it possible to generate .proto file from a Descriptors.Descriptor instance? Maybe I can try to generate the classes by calling protoc command from my program, compile and load them to the program using Class.forName API.

--
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+unsubscribe <at> googlegroups.com.
To post to this group, send email to protobuf <at> googlegroups.com.
Visit this group at http://groups.google.com/group/protobuf.
For more options, visit https://groups.google.com/d/optout.

Gmane