[protobuf] Re: Issue 630 in protobuf: Java: initializing bitFields variables

2014-04-15 Thread protobuf
Comment #5 on issue 630 by kral.voj...@gmail.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 And just quick wondering why are the other number types properties not set as bitFields so by JVM only without the setting in initialization

[protobuf] Re: Issue 630 in protobuf: Java: initializing bitFields variables

2014-04-15 Thread protobuf
Comment #4 on issue 630 by xiaof...@google.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 If you are implementing your own parsing methods, it's better to only use public methods (e.g., clear() when you want to reset a mesasge). Int

[protobuf] Re: Issue 630 in protobuf: Java: initializing bitFields variables

2014-04-15 Thread protobuf
Comment #3 on issue 630 by kral.voj...@gmail.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 Ok, I needed different behavior from the parsing so I had to call it by myself and I noticed this handling of bitFields and since I was not sure

[protobuf] Re: Issue 630 in protobuf: Java: initializing bitFields variables

2014-04-15 Thread protobuf
Comment #2 on issue 630 by kral.voj...@gmail.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 Ok, I needed different behavior from the parsing so I had to call it by myself and I noticed this handling of bitFields and since I was not sure

[protobuf] Re: Issue 630 in protobuf: Java: initializing bitFields variables

2014-04-15 Thread protobuf
Updates: Status: WorkingAsIntended Comment #1 on issue 630 by xiaof...@google.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 This is working as intended. bitFields should be initialized to all zeros and it's reasonable to n

[protobuf] Issue 630 in protobuf: Java: initializing bitFields variables

2014-04-15 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 630 by kral.voj...@gmail.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 What steps will reproduce the problem? 1. Generate Java class What is the expected output? What

[protobuf] Re: Issue 57 in protobuf: null values should be treated as no value

2014-04-14 Thread protobuf
Comment #46 on issue 57 by ag.coolg...@gmail.com: null values should be treated as no value http://code.google.com/p/protobuf/issues/detail?id=57 To have null in proto buffer, can workaround be something like wrapping the value and type of value(null/non-null) into a message and then send

[protobuf] Re: Issue 57 in protobuf: null values should be treated as no value

2014-04-14 Thread protobuf
Comment #45 on issue 57 by ankit.ga...@gmail.com: null values should be treated as no value http://code.google.com/p/protobuf/issues/detail?id=57 To have null in proto buffer, can workaround me something like wrapping the value and type of value(null/non-null) into a message and then send

[protobuf] Issue 629 in protobuf: compile protobuf2.3.0,2.4.1 on aix5.3,error happened when i make

2014-04-07 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 629 by yanwujiu...@gmail.com: compile protobuf2.3.0,2.4.1 on aix5.3,error happened when i make http://code.google.com/p/protobuf/issues/detail?id=629 What steps will reproduce the problem? 1.configure

[protobuf] Re: Issue 476 in protobuf: please document how to use protobuf with maven

2014-04-06 Thread protobuf
Comment #9 on issue 476 by plind...@google.com: please document how to use protobuf with maven http://code.google.com/p/protobuf/issues/detail?id=476 I'd be happy to shepherd any maven patches into the protobuf core and/or assist with delegation of the namespace. I recently landed pa

[protobuf] Issue 628 in protobuf: Update ThirdPartyAddOns link to protobuf-c

2014-04-05 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 628 by robert.e...@gmail.com: Update ThirdPartyAddOns link to protobuf-c http://code.google.com/p/protobuf/issues/detail?id=628 Hi, The protobuf-c project has moved from http://code.google.com/p/protobuf-c/ to https

[protobuf] Issue 627 in protobuf: Could we host proto.vim in a separate project?

2014-04-04 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 627 by dbarn...@google.com: Could we host proto.vim in a separate project? http://code.google.com/p/protobuf/issues/detail?id=627 I'd like to push a version of the vim syntax file to a standalone g

[protobuf] Re: Issue 370 in protobuf: static initialization problem with dlopen

2014-04-03 Thread protobuf
Comment #12 on issue 370 by scpet...@osrfoundation.org: static initialization problem with dlopen http://code.google.com/p/protobuf/issues/detail?id=370 The patch in comment #10 works for us as well. Is there any chance that it will be merged? I can generate some code to help reproduce the

[protobuf] Re: Issue 626 in protobuf: 64bit portability issue

2014-04-02 Thread protobuf
Comment #2 on issue 626 by nio...@gmail.com: 64bit portability issue http://code.google.com/p/protobuf/issues/detail?id=626 'return' conversion from '__int64' to 'Int' possible lose of data. run the app on 64bit os lead app crash. -- You received this message beca

[protobuf] Re: Issue 488 in protobuf: powerpc-linux cross compilation not compiling anymore

2014-04-02 Thread protobuf
Comment #6 on issue 488 by wscul...@gmail.com: powerpc-linux cross compilation not compiling anymore http://code.google.com/p/protobuf/issues/detail?id=488 The application of the two patches from this ticket to the current trunk enables a build on powerpc64 linux which otherwise fails with

[protobuf] Re: Issue 626 in protobuf: 64bit portability issue

2014-04-02 Thread protobuf
Comment #1 on issue 626 by xiaof...@google.com: 64bit portability issue http://code.google.com/p/protobuf/issues/detail?id=626 What's the compile error? I think we can and a static_cast to suppress the error message. There is no chance the index can be larger than 32bit. -- You rec

[protobuf] Issue 626 in protobuf: 64bit portability issue

2014-04-02 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 626 by nio...@gmail.com: 64bit portability issue http://code.google.com/p/protobuf/issues/detail?id=626 What steps will reproduce the problem? 1.Function 'int index() const' in class of &

[protobuf] Re: Issue 434 in protobuf: With PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while child still exists: causes segmentation fault

2014-04-01 Thread protobuf
Comment #10 on issue 434 by adam.gra...@upverter.com: With PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp, parent object deleted while child still exists: causes segmentation fault http://code.google.com/p/protobuf/issues/detail?id=434 A fix for this is crucial for us. I would be tempted to

[protobuf] Issue 625 in protobuf: Exception safety issues in RepeatedPtrField

2014-04-01 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 625 by f.volej...@gmail.com: Exception safety issues in RepeatedPtrField http://code.google.com/p/protobuf/issues/detail?id=625 Hello, the method RepeatedPtrFieldBase::Add has a exception safety problem

[protobuf] Issue 624 in protobuf: MSVC 12.0 solution compile issue.

2014-03-30 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 624 by nsampie...@gmail.com: MSVC 12.0 solution compile issue. http://code.google.com/p/protobuf/issues/detail?id=624 What steps will reproduce the problem? 1. Download and uncompress the last source. 2. Try to

[protobuf] Re: Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-27 Thread protobuf
Comment #6 on issue 622 by veer...@gmail.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 Hi, I did not understand pom.xml file. issue what i raised is when we get request, how can we get the country

[protobuf] Re: Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-27 Thread protobuf
Comment #5 on issue 622 by xiaof...@google.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 Hi alx.zykoff, can you create a separate issue for the pom.xml problem? Thanks. -- You received this

[protobuf] Re: Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-27 Thread protobuf
Comment #4 on issue 622 by alx.zyk...@gmail.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 hi in pom.xml (http://code.google.com/p/protobuf/downloads/detail?name=protobuf-2.5.0.tar.bz2&can

[protobuf] Re: Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-26 Thread protobuf
Updates: Status: OutOfScope Comment #3 on issue 622 by xiaof...@google.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 This is the protobuf issue tracker. You probably want to post AdWords API

[protobuf] Re: Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-26 Thread protobuf
Comment #2 on issue 622 by veer...@gmail.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 Geographical Targeting file issue. -- You received this message because this project is configured to send all

[protobuf] Re: Issue 623 in protobuf: Hot to check the latency when using Python Script to send Bid Requests

2014-03-26 Thread protobuf
Comment #1 on issue 623 by xiaof...@google.com: Hot to check the latency when using Python Script to send Bid Requests http://code.google.com/p/protobuf/issues/detail?id=623 Hi, I think you are posting to the wrong place. Probably you want to post questions in this forum: https

[protobuf] Re: Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-26 Thread protobuf
Comment #1 on issue 622 by xiaof...@google.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 Is this a protobuf issue? -- You received this message because this project is configured to send all issue

[protobuf] Issue 623 in protobuf: Hot to check the latency when using Python Script to send Bid Requests

2014-03-26 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 623 by veer...@gmail.com: Hot to check the latency when using Python Script to send Bid Requests http://code.google.com/p/protobuf/issues/detail?id=623 Hi, Hot to check the latency when using Python Script

[protobuf] Issue 622 in protobuf: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id

2014-03-26 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 622 by veer...@gmail.com: Retrieving Country,Zipcode,postalcode,State and DMA code from geo_criteria_id http://code.google.com/p/protobuf/issues/detail?id=622 Hi, We are trying to get Country,Zipcode

[protobuf] Issue 621 in protobuf: Python library does not run setup.py under a Python 3.x interpreter

2014-03-25 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 621 by sta...@gmail.com: Python library does not run setup.py under a Python 3.x interpreter http://code.google.com/p/protobuf/issues/detail?id=621 What steps will reproduce the problem? 1. Run setup.py with

[protobuf] Re: Issue 619 in protobuf: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString()

2014-03-25 Thread protobuf
Updates: Status: Accepted Comment #3 on issue 619 by xiaof...@google.com: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString() http://code.google.com/p/protobuf/issues/detail?id=619 ok, so the problem is that we should register a shut

[protobuf] Re: Issue 619 in protobuf: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString()

2014-03-25 Thread protobuf
Comment #2 on issue 619 by berthold...@googlemail.com: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString() http://code.google.com/p/protobuf/issues/detail?id=619 Hallo, I provide you with the collected files of my investigations. I hope

[protobuf] Re: Issue 620 in protobuf: Concerting ByteString to String

2014-03-24 Thread protobuf
Comment #4 on issue 620 by veer...@gmail.com: Concerting ByteString to String http://code.google.com/p/protobuf/issues/detail?id=620 Hi, I am not getting any error but not able to convert ID and IPAddress. Let us say when i want to augment, basically by IP will be getting City,Zipcode

[protobuf] Re: Issue 620 in protobuf: Concerting ByteString to String

2014-03-24 Thread protobuf
Comment #3 on issue 620 by xiaof...@google.com: Concerting ByteString to String http://code.google.com/p/protobuf/issues/detail?id=620 What's the code that leads to your reported error: Actual ID Value: [B@65abc63a Expected O/P: "Mv\2005\000\017.\001\n\345\177\307X\200M8"

[protobuf] Re: Issue 620 in protobuf: Concerting ByteString to String

2014-03-24 Thread protobuf
Comment #2 on issue 620 by veer...@gmail.com: Concerting ByteString to String http://code.google.com/p/protobuf/issues/detail?id=620 attached is the protobuff file and below is the code for the conversion public static String AdXRequest(Object O, Concept req) { String ps

[protobuf] Re: Issue 620 in protobuf: Concerting ByteString to String

2014-03-24 Thread protobuf
Comment #1 on issue 620 by xiaof...@google.com: Concerting ByteString to String http://code.google.com/p/protobuf/issues/detail?id=620 What's the proto definition and what's the code converting the message to string format? -- You received this message because this project is

[protobuf] Re: Issue 607 in protobuf: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion

2014-03-24 Thread protobuf
Updates: Status: Fixed Comment #4 on issue 607 by xiaof...@google.com: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 Committed as r521 -- You received this message because this project is

[protobuf] Re: Issue 619 in protobuf: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString()

2014-03-24 Thread protobuf
Comment #1 on issue 619 by xiaof...@google.com: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString() http://code.google.com/p/protobuf/issues/detail?id=619 Can you narrow down the cause and provide us a simple source file that can reproduce

[protobuf] Re: Issue 616 in protobuf: zero_copy_stream_impl_lite.cc needs for min/max definitions

2014-03-24 Thread protobuf
Updates: Status: Duplicate Mergedinto: 531 Comment #3 on issue 616 by xiaof...@google.com: zero_copy_stream_impl_lite.cc needs for min/max definitions http://code.google.com/p/protobuf/issues/detail?id=616 (No comment was entered for this change.) -- You received this

[protobuf] Re: Issue 531 in protobuf: Cannot build protobuf using VS2013

2014-03-24 Thread protobuf
Comment #9 on issue 531 by xiaof...@google.com: Cannot build protobuf using VS2013 http://code.google.com/p/protobuf/issues/detail?id=531 Issue 616 has been merged into this issue. -- You received this message because this project is configured to send all issue notifications to this

[protobuf] Re: Issue 606 in protobuf: Small issue building under Win32

2014-03-24 Thread protobuf
Updates: Status: Fixed Comment #2 on issue 606 by xiaof...@google.com: Small issue building under Win32 http://code.google.com/p/protobuf/issues/detail?id=606 Fixed in r512. Will be included in next release. -- You received this message because this project is configured to send all

[protobuf] Re: Issue 531 in protobuf: Cannot build protobuf using VS2013

2014-03-24 Thread protobuf
Updates: Status: Fixed Comment #8 on issue 531 by xiaof...@google.com: Cannot build protobuf using VS2013 http://code.google.com/p/protobuf/issues/detail?id=531 (No comment was entered for this change.) -- You received this message because this project is configured to send all

[protobuf] Issue 620 in protobuf: Concerting ByteString to String

2014-03-24 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 620 by veer...@gmail.com: Concerting ByteString to String http://code.google.com/p/protobuf/issues/detail?id=620 What steps will reproduce the problem? 1. Sending the Request using Python request 2. Receiving

[protobuf] Re: Issue 607 in protobuf: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion

2014-03-24 Thread protobuf
Comment #3 on issue 607 by gli...@chromium.org: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 Ping? -- You received this message because this project is configured to send all issue notifications

[protobuf] Issue 619 in protobuf: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString()

2014-03-23 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 619 by brave...@webrtc.org: Memoryleak since change const ::std::string kEmptyString to const ::std::string& GetEmptyString() http://code.google.com/p/protobuf/issues/detail?id=619 What steps will repro

[protobuf] Re: Issue 616 in protobuf: zero_copy_stream_impl_lite.cc needs for min/max definitions

2014-03-23 Thread protobuf
Comment #2 on issue 616 by yuk...@google.com: zero_copy_stream_impl_lite.cc needs for min/max definitions http://code.google.com/p/protobuf/issues/detail?id=616 And I guess this is a dup of Issue 531. -- You received this message because this project is configured to send all issue

[protobuf] Re: Issue 606 in protobuf: Small issue building under Win32

2014-03-23 Thread protobuf
Comment #1 on issue 606 by yuk...@google.com: Small issue building under Win32 http://code.google.com/p/protobuf/issues/detail?id=606 See Issue 531. This issue was fixed as r512. Maybe next release will contain the fix. -- You received this message because this project is configured to

[protobuf] Re: Issue 616 in protobuf: zero_copy_stream_impl_lite.cc needs for min/max definitions

2014-03-23 Thread protobuf
Comment #1 on issue 616 by yuk...@google.com: zero_copy_stream_impl_lite.cc needs for min/max definitions http://code.google.com/p/protobuf/issues/detail?id=616 This issue was fixed as r512. Maybe next release will contain the fix. -- You received this message because this project is

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

2014-03-20 Thread protobuf
Comment #6 on issue 493 by lshmouse: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 To keep the compatibility, i do a little hack in getUnknownFields and deploy a new version protobuf-java. It works fine

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

2014-03-17 Thread protobuf
Comment #5 on issue 493 by hisanth...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 protobuf is embedded into many hadoop libraries (pig, hadoop, hive,...), breaking compatibility is definitly

[protobuf] Re: Issue 618 in protobuf: Cannot compile protobuf in Solaris 10 x86

2014-03-14 Thread protobuf
Comment #1 on issue 618 by marvin...@gmail.com: Cannot compile protobuf in Solaris 10 x86 http://code.google.com/p/protobuf/issues/detail?id=618 Here is the config.log in gtest sub-directory Attachments: gtest-config.log 7.0 KB -- You received this message because this project is

[protobuf] Issue 618 in protobuf: Cannot compile protobuf in Solaris 10 x86

2014-03-14 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 618 by marvin...@gmail.com: Cannot compile protobuf in Solaris 10 x86 http://code.google.com/p/protobuf/issues/detail?id=618 What steps will reproduce the problem? 1. ./configure (under root) 2. 3. What is

[protobuf] Issue 617 in protobuf: Protobuf fails to build on Linux/SPARC

2014-03-13 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 617 by ivan.the...@gmail.com: Protobuf fails to build on Linux/SPARC http://code.google.com/p/protobuf/issues/detail?id=617 What steps will reproduce the problem? 1. Fetch protobuf 2.5.0 or svn r518. 2

[protobuf] Issue 616 in protobuf: zero_copy_stream_impl_lite.cc needs for min/max definitions

2014-03-13 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 616 by bruce.c...@gmail.com: zero_copy_stream_impl_lite.cc needs for min/max definitions http://code.google.com/p/protobuf/issues/detail?id=616 What steps will reproduce the problem? 1. Try and build using

[protobuf] Re: Issue 464 in protobuf: Inefficient Java handling of repeated list of primitive types

2014-03-13 Thread protobuf
Comment #3 on issue 464 by won...@gmail.com: Inefficient Java handling of repeated list of primitive types http://code.google.com/p/protobuf/issues/detail?id=464 Hi, We had the same issue at Two Sigma, so we developed a patch that *does not* adds any dependency. It passes all the unit

[protobuf] Re: Issue 615 in protobuf: misleading document in python api

2014-03-13 Thread protobuf
Updates: Status: Accepted Comment #1 on issue 615 by xiaof...@google.com: misleading document in python api http://code.google.com/p/protobuf/issues/detail?id=615 (No comment was entered for this change.) -- You received this message because this project is configured to send all

[protobuf] Issue 615 in protobuf: misleading document in python api

2014-03-12 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 615 by ccpp...@gmail.com: misleading document in python api http://code.google.com/p/protobuf/issues/detail?id=615 The document for python api ParseFromString is misleading as following: def ParseFromString(self

[protobuf] Issue 614 in protobuf: ByteString: Method For Chunking

2014-03-12 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 614 by vi...@umich.edu: ByteString: Method For Chunking http://code.google.com/p/protobuf/issues/detail?id=614 The internal usage of RopeByteString (and RopeInputStream) is particularly interesting. Alongside

[protobuf] Re: Issue 406 in protobuf: Generated code fails to compile on OpenBSD

2014-03-09 Thread protobuf
Comment #5 on issue 406 by peterjne...@gmail.com: Generated code fails to compile on OpenBSD http://code.google.com/p/protobuf/issues/detail?id=406 Correction, this does actually need the -isystem bit removed to work on OpenBSD. -- You received this message because this project is

[protobuf] Re: Issue 406 in protobuf: Generated code fails to compile on OpenBSD

2014-03-07 Thread protobuf
Comment #4 on issue 406 by peterjne...@gmail.com: Generated code fails to compile on OpenBSD http://code.google.com/p/protobuf/issues/detail?id=406 I work with Simon on the same project and the issue came up again. After a bit of digging I found this link, which talks about the prefix

[protobuf] Issue 613 in protobuf: protoc: Add options to redirect input / output to files.

2014-03-06 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 613 by ppra...@google.com: protoc: Add options to redirect input / output to files. http://code.google.com/p/protobuf/issues/detail?id=613 What is the problem? When used with --encode / --decode

[protobuf] Re: Issue 612 in protobuf: Broken link to documentation on "UserGuide" wiki page on code.google.com

2014-03-06 Thread protobuf
Updates: Status: Fixed Comment #1 on issue 612 by xiaof...@google.com: Broken link to documentation on "UserGuide" wiki page on code.google.com http://code.google.com/p/protobuf/issues/detail?id=612 I just updated the link to the correct address: https://developers.

[protobuf] Issue 612 in protobuf: Broken link to documentation on "UserGuide" wiki page on code.google.com

2014-03-05 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 612 by volkersi...@gmail.com: Broken link to documentation on "UserGuide" wiki page on code.google.com http://code.google.com/p/protobuf/issues/detail?id=612 What steps will reproduce the problem?

[protobuf] Issue 611 in protobuf: Python proto optimization

2014-03-03 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 611 by patr...@dropbox.com: Python proto optimization http://code.google.com/p/protobuf/issues/detail?id=611 (original thread) https://groups.google.com/forum/#!topic/protobuf/RDAKafkfXYM I wrote a patch which optimize

[protobuf] Issue 609 in protobuf: protoc produces java code with compiler errors when terminating message field names with "field"

2014-02-27 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 609 by jhaf...@gmail.com: protoc produces java code with compiler errors when terminating message field names with "field" http://code.google.com/p/protobuf/issues/detail?id=609 1. Use protoc

[protobuf] Re: Issue 464 in protobuf: Inefficient Java handling of repeated list of primitive types

2014-02-24 Thread protobuf
Comment #2 on issue 464 by anno.lan...@gmail.com: Inefficient Java handling of repeated list of primitive types http://code.google.com/p/protobuf/issues/detail?id=464 I produced a different fix that preserves the immutability of the non-builders and, specifically, does not expose the

[protobuf] Re: Issue 229 in protobuf: TextFormat should have option to silently ignore unknown fields

2014-02-21 Thread protobuf
Comment #2 on issue 229 by k...@spotify.com: TextFormat should have option to silently ignore unknown fields http://code.google.com/p/protobuf/issues/detail?id=229 We use the text format for fixture data in our test cases (we don't want to have binary data in our repository), a

[protobuf] Re: Issue 608 in protobuf: Failed to build 2.5.0, on Win7, Cygwin, MSVS 2012 express

2014-02-20 Thread protobuf
Comment #1 on issue 608 by ce.slate...@gmail.com: Failed to build 2.5.0, on Win7, Cygwin, MSVS 2012 express http://code.google.com/p/protobuf/issues/detail?id=608 Guess I should have tried a clean build from a new download, I was using a 2.5.0 package that I had run VS 2008 on, a clean

[protobuf] Re: Issue 602 in protobuf: Protobuf fails to build on Solaris 10/11

2014-02-20 Thread protobuf
Comment #1 on issue 602 by mm42...@googlemail.com: Protobuf fails to build on Solaris 10/11 http://code.google.com/p/protobuf/issues/detail?id=602 It would be nice to get protobuf working again on FreeBSD/sparc64 also. If anybody needs testing resources for that, ping me. -- You received

[protobuf] Re: Issue 213 in protobuf: libprotobuf.so.6 not found after installation

2014-02-19 Thread protobuf
Comment #20 on issue 213 by nellaivi...@gmail.com: libprotobuf.so.6 not found after installation http://code.google.com/p/protobuf/issues/detail?id=213 I have similar issue in the Cent OS 6.5, ldconfig saved my day. Thanks Kenton. -- You received this message because this project is

[protobuf] Issue 608 in protobuf: Failed to build 2.5.0, on Win7, Cygwin, MSVS 2012 express

2014-02-19 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 608 by ce.slate...@gmail.com: Failed to build 2.5.0, on Win7, Cygwin, MSVS 2012 express http://code.google.com/p/protobuf/issues/detail?id=608 What steps will reproduce the problem? 1.Unpacked Zip, read

[protobuf] Re: Issue 607 in protobuf: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion

2014-02-19 Thread protobuf
Comment #2 on issue 607 by gli...@chromium.org: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 This header comes from the compiler that supports ThreadSanitizer (that's Clang 3.3+ or GCC 4.7+)

[protobuf] Re: Issue 607 in protobuf: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion

2014-02-18 Thread protobuf
Comment #1 on issue 607 by xiaof...@google.com: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 Where does this header file come from? Does it mean that users will need to install these header files

[protobuf] Re: Issue 575 in protobuf: Google Protobuf will not build under ARM64

2014-02-18 Thread protobuf
Comment #3 on issue 575 by molind: Google Protobuf will not build under ARM64 http://code.google.com/p/protobuf/issues/detail?id=575 I checked on device (iPhone 5s). It works fine with this workaround. -- You received this message because this project is configured to send all issue

[protobuf] Issue 607 in protobuf: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion

2014-02-18 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 607 by gli...@google.com: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 The attached patch replaces the TSan API

[protobuf] Re: Issue 570 in protobuf: build 2.4.1 failed on mac os x 10.9

2014-02-14 Thread protobuf
Comment #8 on issue 570 by msaf...@gmail.com: build 2.4.1 failed on mac os x 10.9 http://code.google.com/p/protobuf/issues/detail?id=570 Adding #include worked for me as well. -- You received this message because this project is configured to send all issue notifications to this address

[protobuf] Re: Issue 488 in protobuf: powerpc-linux cross compilation not compiling anymore

2014-02-13 Thread protobuf
Comment #5 on issue 488 by andrew.i...@gmail.com: powerpc-linux cross compilation not compiling anymore http://code.google.com/p/protobuf/issues/detail?id=488 AArch64 is becoming more widely available. -- You received this message because this project is configured to send all issue

[protobuf] Re: Issue 605 in protobuf: protoc just segfaults on FreeBSD 10-RELEASE arm

2014-02-12 Thread protobuf
Comment #1 on issue 605 by pedrolea...@gmail.com: protoc just segfaults on FreeBSD 10-RELEASE arm http://code.google.com/p/protobuf/issues/detail?id=605 protobuf 2.4.1 successfully built on the same system. -- You received this message because this project is configured to send all issue

[protobuf] Issue 606 in protobuf: Small issue building under Win32

2014-02-12 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 606 by ramon.ga...@gmail.com: Small issue building under Win32 http://code.google.com/p/protobuf/issues/detail?id=606 I have a small issue building protocol buffers 2.5.0 under Visual Studio Express 2013 The file

[protobuf] Re: Issue 57 in protobuf: null values should be treated as no value

2014-02-08 Thread protobuf
Comment #44 on issue 57 by osu...@gmail.com: null values should be treated as no value http://code.google.com/p/protobuf/issues/detail?id=57 Interesting thread. I love protobuf. I think the foundation of the disagreement is in comment #33: "[We] do not like the idea of treating "

[protobuf] Issue 605 in protobuf: protoc just segfaults on FreeBSD 10-RELEASE arm

2014-02-08 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 605 by pedrolea...@gmail.com: protoc just segfaults on FreeBSD 10-RELEASE arm http://code.google.com/p/protobuf/issues/detail?id=605 What steps will reproduce the problem? 1. FreeBSD on a raspberry pi (or

[protobuf] Issue 604 in protobuf: Option to include stdfix.h in output cc files.

2014-02-07 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 604 by mikio...@gmail.com: Option to include stdfix.h in output cc files. http://code.google.com/p/protobuf/issues/detail?id=604 for visual studio projects with precompiled headers option on -- You received this message

[protobuf] Re: Issue 603 in protobuf: descriptor.proto: suggest add go_generic_services optional for golang.

2014-02-05 Thread protobuf
Comment #1 on issue 603 by chaishus...@gmail.com: descriptor.proto: suggest add go_generic_services optional for golang. http://code.google.com/p/protobuf/issues/detail?id=603 add: optional bool go_generic_services = 19 [default=false]; Attachments: add_go_generic_services.patch

[protobuf] Issue 603 in protobuf: descriptor.proto: suggest add go_generic_services optional for golang.

2014-02-03 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 603 by chaishus...@gmail.com: descriptor.proto: suggest add go_generic_services optional for golang. http://code.google.com/p/protobuf/issues/detail?id=603 In SVN r425, the go_package optional has been added

[protobuf] Issue 602 in protobuf: Protobuf fails to build on Solaris 10/11

2014-02-02 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 602 by j.l.ols...@gmail.com: Protobuf fails to build on Solaris 10/11 http://code.google.com/p/protobuf/issues/detail?id=602 What steps will reproduce the problem? 1. Try to build on Solaris 10/11 with GCC or

[protobuf] Re: Issue 570 in protobuf: build 2.4.1 failed on mac os x 10.9

2014-01-31 Thread protobuf
Comment #7 on issue 570 by getae...@gmail.com: build 2.4.1 failed on mac os x 10.9 http://code.google.com/p/protobuf/issues/detail?id=570 "Adding #include " solution worked for me -- You received this message because this project is configured to send all issue notificatio

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-31 Thread protobuf
Comment #7 on issue 515 by peterhan...@yahoo.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 The proposed solution doesn't work because: 1. The name of the enum type is changed from "Foo" to "Foo::Enum" which will be confusing to

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-30 Thread protobuf
Comment #6 on issue 515 by xiaof...@google.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 Disallowing C++11 features is more of a policy issue rather than a technical one. The policy will eventually change but so far I haven't seen any move in

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-30 Thread protobuf
Comment #5 on issue 515 by cbsm...@gmail.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 Why not put it in now with a flag or an #ifdef on the C++ version? -- You received this message because this project is configured to send all issue notifications to

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-30 Thread protobuf
Comment #4 on issue 515 by xiaof...@google.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 I think the support for C++11 enum class is a good feature to have. We'll need to wait for some time though, as we currently still prohibit C++11 featur

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-30 Thread protobuf
Comment #3 on issue 515 by kara...@gmail.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 Instead of `namespace Bar { enum ...`, we could use `enum class Bar ...', or perhaps `struct Bar { enum ...`. For myself, I don't care much about duplicated

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-30 Thread protobuf
Comment #2 on issue 515 by xiaof...@google.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 The proposed solution doesn't work because: 1. The name of the enum type is changed from "Foo" to "Foo::Enum" which will be confusing to the u

[protobuf] Re: Issue 515 in protobuf: More intelligent enums

2014-01-30 Thread protobuf
Comment #1 on issue 515 by joew...@live.com: More intelligent enums http://code.google.com/p/protobuf/issues/detail?id=515 I would say the option name is a little language specific, but the idea is good. Maybe call it "scoped=true" or something similar and add a command-line prot

[protobuf] Re: Issue 596 in protobuf: protoc cannot decode files larger than 67108864 bytes

2014-01-28 Thread protobuf
Comment #1 on issue 596 by jrolt...@gmail.com: protoc cannot decode files larger than 67108864 bytes http://code.google.com/p/protobuf/issues/detail?id=596 I get "failed to parse input" with a small file too - not just a very large one. Are you having issues with just big fi

[protobuf] Issue 601 in protobuf: include files are not compiling properly

2014-01-25 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 601 by chaudhar...@gmail.com: include files are not compiling properly http://code.google.com/p/protobuf/issues/detail?id=601 What steps will reproduce the problem? 1. i buiilded google protocol in solaris X86 32 bit

[protobuf] Re: Issue 599 in protobuf: Fails to compile for Intel Phi

2014-01-23 Thread protobuf
Comment #1 on issue 599 by pe...@quux.net: Fails to compile for Intel Phi http://code.google.com/p/protobuf/issues/detail?id=599 Thanks Stephen. ICC supports GCC's inline assembly syntax. I've applied your suggestion and tested it. An updated patch is attached. /peter A

[protobuf] Issue 600 in protobuf: Add a flag to generate C++ includes using "" instead of <>

2014-01-21 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 600 by amis...@google.com: Add a flag to generate C++ includes using "" instead of <> http://code.google.com/p/protobuf/issues/detail?id=600 Right now, the generated C++ code uses #include <

[protobuf] Issue 599 in protobuf: Fails to compile for Intel Phi

2014-01-21 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 599 by pe...@quux.net: Fails to compile for Intel Phi http://code.google.com/p/protobuf/issues/detail?id=599 What steps will reproduce the problem? 1. Install Intel Composer XE with Intel Xeon Phi support 2

[protobuf] Re: Issue 597 in protobuf: Add sbt-cppp to ThirdPartyAddOns wiki page, please

2014-01-21 Thread protobuf
Updates: Status: Fixed Comment #1 on issue 597 by xiaof...@google.com: Add sbt-cppp to ThirdPartyAddOns wiki page, please http://code.google.com/p/protobuf/issues/detail?id=597 Done. Added to the "Other utilities" section. -- You received this message because this

[protobuf] Re: Issue 598 in protobuf: unused parameter warnings

2014-01-21 Thread protobuf
Updates: Status: Accepted Comment #1 on issue 598 by liuj...@google.com: unused parameter warnings http://code.google.com/p/protobuf/issues/detail?id=598 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue

<    1   2   3   4   5   6   7   8   9   10   >