[protobuf] Issue 657 in protobuf: Unnecessary dependency against protobuf in third-level targets.

2014-07-20 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 657 by abys...@gmail.com: Unnecessary dependency against protobuf in third-level targets. http://code.google.com/p/protobuf/issues/detail?id=657 I have C++ generated file, say `a.pb.cc`, and I link it into shared library

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

2014-07-18 Thread protobuf
Updates: Status: WontFix Owner: jie...@google.com Comment #1 on issue 609 by jie...@google.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 Thanks for repo

[protobuf] Re: Issue 576 in protobuf: please add TextFormat.printUnicode() or open class Printer

2014-07-17 Thread protobuf
Updates: Status: Accepted Owner: jie...@google.com Comment #3 on issue 576 by jie...@google.com: please add TextFormat.printUnicode() or open class Printer http://code.google.com/p/protobuf/issues/detail?id=576 (No comment was entered for this change.) -- You received this

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

2014-07-17 Thread protobuf
Updates: Labels: FixedIn-2.6.0 Comment #3 on issue 598 by jie...@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

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

2014-07-17 Thread protobuf
Updates: Status: Fixed Comment #2 on issue 598 by jie...@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

[protobuf] Re: Issue 641 in protobuf: Lots of "implicit conversion loses precision" errors.

2014-07-17 Thread protobuf
Comment #1 on issue 641 by jie...@google.com: Lots of "implicit conversion loses precision" errors. http://code.google.com/p/protobuf/issues/detail?id=641 Issue 631 has been merged into this issue. -- You received this message because this project is configured to send a

[protobuf] Re: Issue 631 in protobuf: Fixing issue #641

2014-07-17 Thread protobuf
Updates: Status: Duplicate Mergedinto: 641 Comment #2 on issue 631 by jie...@google.com: Fixing issue #641 http://code.google.com/p/protobuf/issues/detail?id=631 (No comment was entered for this change.) -- You received this message because this project is configured to send

[protobuf] Re: Issue 636 in protobuf: Bug in com.google.protobuf.TextFormat.TextGenerator.print()

2014-07-17 Thread protobuf
Updates: Status: Started Owner: jie...@google.com Labels: FixedIn-2.6.0 Comment #2 on issue 636 by jie...@google.com: Bug in com.google.protobuf.TextFormat.TextGenerator.print() http://code.google.com/p/protobuf/issues/detail?id=636 Thanks for reporting this -- You

[protobuf] Re: Issue 654 in protobuf: Code bloat caused by repeated_field.h #include'ing

2014-07-17 Thread protobuf
Updates: Status: Started Owner: jie...@google.com Labels: FixedIn-2.6.0 Comment #3 on issue 654 by jie...@google.com: Code bloat caused by repeated_field.h #include'ing http://code.google.com/p/protobuf/issues/detail?id=654 Thanks for reporting this -- You rec

[protobuf] Re: Issue 429 in protobuf: Support ByteBuffer in CodedInputStream and CodedOutputStream to avoid redundant copies for direct ByteBuffer.

2014-07-17 Thread protobuf
Updates: Owner: jie...@google.com Comment #5 on issue 429 by jie...@google.com: Support ByteBuffer in CodedInputStream and CodedOutputStream to avoid redundant copies for direct ByteBuffer. http://code.google.com/p/protobuf/issues/detail?id=429 (No comment was entered for this

[protobuf] Re: Issue 656 in protobuf: Example protobuf uses required fields

2014-07-17 Thread protobuf
Updates: Owner: jie...@google.com Comment #2 on issue 656 by jie...@google.com: Example protobuf uses required fields http://code.google.com/p/protobuf/issues/detail?id=656 (No comment was entered for this change.) -- You received this message because this project is configured to

[protobuf] Re: Issue 656 in protobuf: Example protobuf uses required fields

2014-07-17 Thread protobuf
Updates: Status: WontFix Comment #1 on issue 656 by jie...@google.com: Example protobuf uses required fields http://code.google.com/p/protobuf/issues/detail?id=656 Just show users how to use it, so we covered the basic required, optional and repeated. It also helps for the testing

[protobuf] Re: Issue 429 in protobuf: Support ByteBuffer in CodedInputStream and CodedOutputStream to avoid redundant copies for direct ByteBuffer.

2014-07-17 Thread protobuf
Updates: Status: Fixed Labels: FixedIn-2.6.0 Comment #4 on issue 429 by jie...@google.com: Support ByteBuffer in CodedInputStream and CodedOutputStream to avoid redundant copies for direct ByteBuffer. http://code.google.com/p/protobuf/issues/detail?id=429 (No comment was

[protobuf] Issue 656 in protobuf: Example protobuf uses required fields

2014-07-16 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 656 by hirshlei...@google.com: Example protobuf uses required fields http://code.google.com/p/protobuf/issues/detail?id=656 What steps will reproduce the problem? 1. Look at the example protobuf definition on

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

2014-07-13 Thread protobuf
Comment #2 on issue 605 by v1ne...@gmail.com: protoc just segfaults on FreeBSD 10-RELEASE arm http://code.google.com/p/protobuf/issues/detail?id=605 This also occurs on FreeBSD 11 on Cubieboard2. Although this could also be a clang issue, I'll try building with GCC. -- You received

[protobuf] Issue 655 in protobuf: String corruption

2014-07-11 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 655 by simon...@gmail.com: String corruption http://code.google.com/p/protobuf/issues/detail?id=655 I am seeing an issue with string corruption under very specific circumstances. My Proto file: message

[protobuf] Re: Issue 654 in protobuf: Code bloat caused by repeated_field.h #include'ing

2014-07-11 Thread protobuf
Comment #2 on issue 654 by mohit.a...@gmail.com: Code bloat caused by repeated_field.h #include'ing http://code.google.com/p/protobuf/issues/detail?id=654 Just removing '#include ' from repeated_field.h reduced our compilation times by 10% throughout. The reason was that

[protobuf] Re: Issue 654 in protobuf: Code bloat caused by repeated_field.h #include'ing

2014-07-11 Thread protobuf
Comment #1 on issue 654 by mohit.a...@gmail.com: Code bloat caused by repeated_field.h #include'ing http://code.google.com/p/protobuf/issues/detail?id=654 Just removing repeated_field.h reduced our compilation times by 10% throughout. The reason was that most .h or .cc files included

[protobuf] Issue 654 in protobuf: Code bloat caused by repeated_field.h #include'ing

2014-07-10 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 654 by mohit.a...@gmail.com: Code bloat caused by repeated_field.h #include'ing http://code.google.com/p/protobuf/issues/detail?id=654 What steps will reproduce the problem? 1. Try preprocessing a .

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

2014-07-10 Thread protobuf
Updates: Owner: jie...@google.com Labels: FixedIn-2.6.0 Comment #13 on issue 434 by xiaof...@google.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

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

2014-07-10 Thread protobuf
Comment #12 on issue 434 by xiaof...@google.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 We are working a new release (2.6.0) right now and it will

[protobuf] Re: Issue 653 in protobuf: Repeated fields in python do not implement the "index()" function

2014-07-10 Thread protobuf
Comment #1 on issue 653 by ajkinn...@gmail.com: Repeated fields in python do not implement the "index()" function http://code.google.com/p/protobuf/issues/detail?id=653 Correction to expected output: Return the *index of the* matching value from the repeated field list, or Val

[protobuf] Issue 653 in protobuf: Repeated fields in python do not implement the "index()" function

2014-07-10 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 653 by ajkinn...@gmail.com: Repeated fields in python do not implement the "index()" function http://code.google.com/p/protobuf/issues/detail?id=653 What steps will reproduce the problem? 1. Define

[protobuf] Issue 652 in protobuf: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found

2014-07-10 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 652 by lawr.es...@gmail.com: fatal error: -fuse-linker-plugin, but liblto_plugin.so not found http://code.google.com/p/protobuf/issues/detail?id=652 What steps will reproduce the problem? 1. download protobuf

[protobuf] Re: Issue 650 in protobuf: Clang barks at file->options() != NULL

2014-07-09 Thread protobuf
Comment #2 on issue 650 by tha...@chromium.org: Clang barks at file->options() != NULL http://code.google.com/p/protobuf/issues/detail?id=650 The line this fires on has been deleted in the google-internal version of protobuf. -- You received this message because this project

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

2014-07-08 Thread protobuf
Comment #7 on issue 488 by lawr.es...@gmail.com: powerpc-linux cross compilation not compiling anymore http://code.google.com/p/protobuf/issues/detail?id=488 After apply 2 patches return following: 0001-Add-generic-GCC-support-for-atomic-operations.patch 0001-Add-generic-gcc-header-to

[protobuf] Issue 651 in protobuf: Patch for /trunk/src/google/protobuf/stubs/platform_macros.h

2014-07-08 Thread protobuf
Status: New Owner: Labels: Type-Patch New issue 651 by lawr.es...@gmail.com: Patch for /trunk/src/google/protobuf/stubs/platform_macros.h http://code.google.com/p/protobuf/issues/detail?id=651 ppc64 support Attachments: platform_macros.h.patch 421 bytes -- You received this

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

2014-07-07 Thread protobuf
Comment #7 on issue 607 by nialldouglas14: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 Correct, Ubuntu's clang supports ThreadSanitiser but without the header file mentioned. You can see t

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

2014-07-07 Thread protobuf
Comment #6 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 Hi Niall, Do you mean the Clang version you installed supports ThreadSanitizer but without header file

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

2014-07-07 Thread protobuf
Comment #5 on issue 607 by nialldouglas14: Replace TSan API declarations in atomicops_internals_tsan.h with a header inclusion http://code.google.com/p/protobuf/issues/detail?id=607 Can you revert this patch please? I don't have the header file sanitizer/tsan_interface_atomic.h

[protobuf] Re: Issue 635 in protobuf: Min and max not defined under Windows/Intel C++

2014-07-04 Thread protobuf
Comment #1 on issue 635 by yuk...@google.com: Min and max not defined under Windows/Intel C++ http://code.google.com/p/protobuf/issues/detail?id=635 Could be a duplicate of Issue 531 and Issue 616. If so, the fix has already been available as r512. -- You received this message because

[protobuf] Re: Issue 593 in protobuf: FatalException on calling SerializeAsString()

2014-07-02 Thread protobuf
Comment #4 on issue 593 by dave.b...@gmail.com: FatalException on calling SerializeAsString() http://code.google.com/p/protobuf/issues/detail?id=593 This exact same issue occurs for me too - and when I replace the usage of all bools with uint32s, the problem goes away. Looking through

[protobuf] Re: Issue 269 in protobuf: Would like to have byte or int8 type for the message definition

2014-06-30 Thread protobuf
Comment #4 on issue 269 by thecodem...@gmail.com: Would like to have byte or int8 type for the message definition http://code.google.com/p/protobuf/issues/detail?id=269 I don't need a fixed length string; I want to encode RGB or RGBA data as 3 or 4 bytes. I could pack them into an

[protobuf] Re: Issue 650 in protobuf: Clang barks at file->options() != NULL

2014-06-30 Thread protobuf
Issue 650: Clang barks at file->options() != NULL http://code.google.com/p/protobuf/issues/detail?id=650 This issue is now blocking issue chromium:381910. See http://code.google.com/p/chromium/issues/detail?id=381910 -- You received this message because you are listed in the owner or CC fie

[protobuf] Issue 650 in protobuf: Clang barks at file->options() != NULL

2014-06-30 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 650 by gli...@chromium.org: Clang barks at file->options() != NULL http://code.google.com/p/protobuf/issues/detail?id=650 With the ToT Clang the following warning is reported when I'm trying to build

[protobuf] Re: Issue 649 in protobuf: Windows: IE Dev Channel (App-V?) causes protobuf tests to fail on the C: drive

2014-06-29 Thread protobuf
Comment #2 on issue 649 by kra...@gmail.com: Windows: IE Dev Channel (App-V?) causes protobuf tests to fail on the C: drive http://code.google.com/p/protobuf/issues/detail?id=649 Updated https://github.com/mumble-voip/mumble-releng/issues/5: It also happens inside junction points. -- You

[protobuf] Re: Issue 360 in protobuf: Precompiled header support

2014-06-29 Thread protobuf
Comment #3 on issue 360 by dmitrinesteruk: Precompiled header support http://code.google.com/p/protobuf/issues/detail?id=360 Upvoting this! -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification

[protobuf] Re: Issue 649 in protobuf: Windows: IE Dev Channel (App-V?) causes protobuf tests to fail on the C: drive

2014-06-29 Thread protobuf
Comment #1 on issue 649 by kra...@gmail.com: Windows: IE Dev Channel (App-V?) causes protobuf tests to fail on the C: drive http://code.google.com/p/protobuf/issues/detail?id=649 See also the upstream bug: https://connect.microsoft.com/IE/feedback/details/909134/unexpected-filesystem

[protobuf] Issue 649 in protobuf: Windows: IE Dev Channel (App-V?) causes protobuf tests to fail on the C: drive

2014-06-29 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 649 by kra...@gmail.com: Windows: IE Dev Channel (App-V?) causes protobuf tests to fail on the C: drive http://code.google.com/p/protobuf/issues/detail?id=649 What steps will reproduce the problem? 1. Install IE dev

[protobuf] Re: Issue 480 in protobuf: Make binary package available for OSX

2014-06-27 Thread protobuf
Comment #2 on issue 480 by jcredl...@googlemail.com: Make binary package available for OSX http://code.google.com/p/protobuf/issues/detail?id=480 When you do it'd be useful if it: supported as many architectures as possible; was compatible with OSX back to 10.6; supported IOS as we

[protobuf] Re: Issue 286 in protobuf: Inconsistency with repeated fields using C++ protobufs

2014-06-26 Thread protobuf
Updates: Owner: jie...@google.com Comment #12 on issue 286 by xiaof...@google.com: Inconsistency with repeated fields using C++ protobufs http://code.google.com/p/protobuf/issues/detail?id=286 Hi robert, I couldn't say for sure when the new release will be out. Our targeted re

[protobuf] Re: Issue 286 in protobuf: Inconsistency with repeated fields using C++ protobufs

2014-06-26 Thread protobuf
Comment #11 on issue 286 by robert.e...@gmail.com: Inconsistency with repeated fields using C++ protobufs http://code.google.com/p/protobuf/issues/detail?id=286 Do you have a firmer expected release date? Debian is expected to freeze in Q4 (November 2014), and I'd like to have th

[protobuf] Re: Issue 286 in protobuf: Inconsistency with repeated fields using C++ protobufs

2014-06-26 Thread protobuf
Comment #10 on issue 286 by xiaof...@google.com: Inconsistency with repeated fields using C++ protobufs http://code.google.com/p/protobuf/issues/detail?id=286 We are working on a new release (2.6) right now. It will include the new python c++ implementation and the old experimental one

[protobuf] Re: Issue 286 in protobuf: Inconsistency with repeated fields using C++ protobufs

2014-06-26 Thread protobuf
Comment #9 on issue 286 by bram.dej...@native-instruments.de: Inconsistency with repeated fields using C++ protobufs http://code.google.com/p/protobuf/issues/detail?id=286 It's already Q2 (almost Q3) 2014. Any update? -- You received this message because this project is configured to

[protobuf] Re: Issue 647 in protobuf: Compilation error on Win 7

2014-06-25 Thread protobuf
Updates: Status: Duplicate Mergedinto: 648 Comment #1 on issue 647 by xiaof...@google.com: Compilation error on Win 7 http://code.google.com/p/protobuf/issues/detail?id=647 (No comment was entered for this change.) -- You received this message because this project is configured

[protobuf] Re: Issue 648 in protobuf: Support for Lua files generation

2014-06-25 Thread protobuf
Comment #2 on issue 648 by xiaof...@google.com: Support for Lua files generation http://code.google.com/p/protobuf/issues/detail?id=648 Issue 647 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 648 in protobuf: Support for Lua files generation

2014-06-25 Thread protobuf
Updates: Status: OutOfScope Comment #1 on issue 648 by xiaof...@google.com: Support for Lua files generation http://code.google.com/p/protobuf/issues/detail?id=648 Lua is not one of the officially supported languages so protoc along can't generate code for that. But you can

[protobuf] Issue 648 in protobuf: Support for Lua files generation

2014-06-24 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 648 by jbbalu...@gmail.com: Support for Lua files generation http://code.google.com/p/protobuf/issues/detail?id=648 What steps will reproduce the problem? 1.Is this protoc-2.5.0-win32 version supports generaton

[protobuf] Issue 647 in protobuf: Compilation error on Win 7

2014-06-24 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 647 by jbbalu...@gmail.com: Compilation error on Win 7 http://code.google.com/p/protobuf/issues/detail?id=647 What steps will reproduce the problem? 1.Used protoc.exe to generate .Lua files from .proto command 2

[protobuf] Issue 646 in protobuf: autogen.sh tries to read from a tape drive on FreeBSD if gtest is not present

2014-06-19 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 646 by ema...@freebsd.org: autogen.sh tries to read from a tape drive on FreeBSD if gtest is not present http://code.google.com/p/protobuf/issues/detail?id=646 autogen.sh invokes 'curl ... | tar jf' which reads

[protobuf] Re: Issue 645 in protobuf: Add link for Gradle Protobuf Plugin to ThridParty page

2014-06-19 Thread protobuf
Updates: Status: Fixed Comment #1 on issue 645 by xiaof...@google.com: Add link for Gradle Protobuf Plugin to ThridParty page http://code.google.com/p/protobuf/issues/detail?id=645 Added to "Other Utilities" section. -- You received this message because this project is con

[protobuf] Issue 645 in protobuf: Add link for Gradle Protobuf Plugin to ThridParty page

2014-06-19 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 645 by aant...@gmail.com: Add link for Gradle Protobuf Plugin to ThridParty page http://code.google.com/p/protobuf/issues/detail?id=645 Add a reference link to Gradle Protobuf Plugin [https://github.com

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

2014-06-17 Thread protobuf
Updates: Status: Fixed Comment #1 on issue 628 by xiaof...@google.com: Update ThirdPartyAddOns link to protobuf-c http://code.google.com/p/protobuf/issues/detail?id=628 (No comment was entered for this change.) -- You received this message because this project is configured to send

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

2014-06-17 Thread protobuf
Comment #16 on issue 493 by sjl...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 I agree with @owen's comments. Yes, it is ideal that all users of hadoop upgrade to the protobuf version tha

[protobuf] Issue 644 in protobuf: when i try to generate the header file for rpc server and client i am getting the following error.

2014-06-16 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 644 by meetmith...@gmail.com: when i try to generate the header file for rpc server and client i am getting the following error. http://code.google.com/p/protobuf/issues/detail?id=644 What steps will

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

2014-06-11 Thread protobuf
Comment #15 on issue 493 by oliver.j...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 protobuf requires that if you have some generated class G that was generated using protoc version V, then G

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

2014-06-11 Thread protobuf
Comment #14 on issue 493 by owen.oma...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 This is more than "can only use one version." Protobuf requires that you run with precisely the vers

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

2014-06-11 Thread protobuf
Comment #13 on issue 493 by oliver.j...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 The "can only use one version" issue is not a problem specific to protobuf; it's a general prob

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

2014-06-11 Thread protobuf
Comment #12 on issue 493 by oliver.j...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 In this case, why doesn't hadoop-mapreduce have a dependency on the library version it requires for co

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

2014-06-11 Thread protobuf
Comment #11 on issue 493 by owen.oma...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 For your own project, regenerating the code is not unreasonable. The problem comes when you use ant/ivy or

[protobuf] Issue 643 in protobuf: Which protocol buffer version shall be used on windows 7 64 bit machine.

2014-06-11 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 643 by vimlesh@gmail.com: Which protocol buffer version shall be used on windows 7 64 bit machine. http://code.google.com/p/protobuf/issues/detail?id=643 What steps will reproduce the problem? 1. build

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

2014-06-10 Thread protobuf
Comment #10 on issue 493 by xiaof...@google.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 Protoc and the runtime together forms the protobuf library. Taking protoc in one version and trying to use it

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

2014-06-10 Thread protobuf
Comment #9 on issue 493 by owen.oma...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 Help us understand why you consider cross version compatibility between the generated code and library

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

2014-06-10 Thread protobuf
Comment #8 on issue 493 by xiaof...@google.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 We don't want to provide this runtime compatibility across different versions. If you are using protoc 2.5

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

2014-06-09 Thread protobuf
Comment #7 on issue 493 by jeag...@gmail.com: protobuf-java (2.5.0) GeneratedMessage#getUnknownFields() not implemented http://code.google.com/p/protobuf/issues/detail?id=493 Can a project member please comment on the patch posted in comment #6. It is a must have to understand what the

[protobuf] Issue 642 in protobuf: Do not support php??

2014-06-06 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 642 by linzuxio...@gmail.com: Do not support php?? http://code.google.com/p/protobuf/issues/detail?id=642 What steps will reproduce the problem? 1. 2. 3. What is the expected output? What do you see instead

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

2014-06-02 Thread protobuf
Comment #21 on issue 213 by danielko...@gmail.com: libprotobuf.so.6 not found after installation http://code.google.com/p/protobuf/issues/detail?id=213 ldconfig fixed my libprotobuf.so.* problem as well, thanks! -- You received this message because this project is configured to send all

[protobuf] Re: Issue 45 in protobuf: build error

2014-05-29 Thread protobuf
Comment #20 on issue 45 by vigneswa...@silvanlabs.com: build error http://code.google.com/p/protobuf/issues/detail?id=45 ./configure --host=arm-linux CC= CXX=compiler g++ path> --with-protoc=< type the path after untaring /protobuf-2.5.0/src/protoc > --prefix= sudo make sud

[protobuf] Re: Issue 45 in protobuf: build error

2014-05-29 Thread protobuf
Comment #19 on issue 45 by vigneswa...@silvanlabs.com: build error http://code.google.com/p/protobuf/issues/detail?id=45 ./configure --host=arm-linux CC=/opt/bbb-angstrom-toolchain/usr/local/angstrom/arm/bin/arm-angstrom-linux-gnueabi-gcc CXX=/opt/bbb-angstrom-toolchain/usr/local/angstrom

[protobuf] Issue 641 in protobuf: Lots of "implicit conversion loses precision" errors.

2014-05-22 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 641 by jetfo...@gmail.com: Lots of "implicit conversion loses precision" errors. http://code.google.com/p/protobuf/issues/detail?id=641 Build with protobuf 2.5.0 for ARM64 (after fixing the platfor

[protobuf] Re: Issue 634 in protobuf: Header file path is wrong in generated .cc files for .proto files in inner directories

2014-05-22 Thread protobuf
Updates: Status: WorkingAsIntended Comment #2 on issue 634 by xiaof...@google.com: Header file path is wrong in generated .cc files for .proto files in inner directories http://code.google.com/p/protobuf/issues/detail?id=634 This is by design. If you want the generated code to

[protobuf] Re: Issue 634 in protobuf: Header file path is wrong in generated .cc files for .proto files in inner directories

2014-05-22 Thread protobuf
Comment #1 on issue 634 by tfar...@chromium.org: Header file path is wrong in generated .cc files for .proto files in inner directories http://code.google.com/p/protobuf/issues/detail?id=634 I don't think this is wrong. Protobuf is generating full path, which imo is a good thing. Ho

[protobuf] Issue 640 in protobuf: OstreamOutputStream destructor can cause double exception.

2014-05-20 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 640 by cld8...@g.rit.edu: OstreamOutputStream destructor can cause double exception. http://code.google.com/p/protobuf/issues/detail?id=640 What steps will reproduce the problem? 1. set Exceptions to badbit

[protobuf] Re: Issue 585 in protobuf: No support compile for Windows Phone 8

2014-05-19 Thread protobuf
Comment #3 on issue 585 by heckfer: No support compile for Windows Phone 8 http://code.google.com/p/protobuf/issues/detail?id=585 Any news ? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification

[protobuf] Re: Issue 585 in protobuf: No support compile for Windows Phone 8

2014-05-19 Thread protobuf
Comment #4 on issue 585 by deivison...@gmail.com: No support compile for Windows Phone 8 http://code.google.com/p/protobuf/issues/detail?id=585 Any news ? Have some one success to do a port to WP8 ? -- You received this message because this project is configured to send all issue

[protobuf] Re: Issue 585 in protobuf: No support compile for Windows Phone 8

2014-05-19 Thread protobuf
Comment #2 on issue 585 by heckfer: No support compile for Windows Phone 8 http://code.google.com/p/protobuf/issues/detail?id=585 Any news ? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification

[protobuf] Re: Issue 639 in protobuf: Protobuf segfaults on attempt to serialize a very large object

2014-05-13 Thread protobuf
Comment #2 on issue 639 by xiaof...@google.com: Protobuf segfaults on attempt to serialize a very large object http://code.google.com/p/protobuf/issues/detail?id=639 Protobuf uses int to represent sizes so the largest size it can possibly support is <2G. We don't have any plan t

[protobuf] Re: Issue 639 in protobuf: Protobuf segfaults on attempt to serialize a very large object

2014-05-13 Thread protobuf
Comment #1 on issue 639 by leonid.g...@gmail.com: Protobuf segfaults on attempt to serialize a very large object http://code.google.com/p/protobuf/issues/detail?id=639 failed to mention - I am just reporting this bug. Both discovery of bug and solution was done by Andrey Pliss. -- You

[protobuf] Issue 639 in protobuf: Protobuf segfaults on attempt to serialize a very large object

2014-05-13 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 639 by leonid.g...@gmail.com: Protobuf segfaults on attempt to serialize a very large object http://code.google.com/p/protobuf/issues/detail?id=639 What steps will reproduce the problem? 1. attempt to

[protobuf] Re: Issue 455 in protobuf: google/protobuf/message.cc is missing #include

2014-05-12 Thread protobuf
Comment #9 on issue 455 by peilin...@gmail.com: google/protobuf/message.cc is missing #include http://code.google.com/p/protobuf/issues/detail?id=455 add the missing include to the message.cc helps -- You received this message because this project is configured to send all issue

[protobuf] Re: Issue 638 in protobuf: Unknown fields are preserved now in python implementation version 2.5.0, but document is out of date.

2014-05-12 Thread protobuf
Updates: Status: Accepted Comment #1 on issue 638 by xiaof...@google.com: Unknown fields are preserved now in python implementation version 2.5.0, but document is out of date. http://code.google.com/p/protobuf/issues/detail?id=638 (No comment was entered for this change.) -- You

[protobuf] Issue 638 in protobuf: Unknown fields are preserved now in python implementation version 2.5.0, but document is out of date.

2014-05-12 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 638 by leexiao...@gmail.com: Unknown fields are preserved now in python implementation version 2.5.0, but document is out of date. http://code.google.com/p/protobuf/issues/detail?id=638 http://code.google.com

[protobuf] Re: Issue 637 in protobuf: Patch for /trunk/src/google/protobuf/stubs/once.cc

2014-05-09 Thread protobuf
Comment #2 on issue 637 by per...@carrosses.com: Patch for /trunk/src/google/protobuf/stubs/once.cc http://code.google.com/p/protobuf/issues/detail?id=637 I have investigated a bit deeper. It's failing on MIPS64 n64 because protobuf doesn't detect MIPS64 architectures, so it t

[protobuf] Re: Issue 637 in protobuf: Patch for /trunk/src/google/protobuf/stubs/once.cc

2014-05-09 Thread protobuf
Comment #1 on issue 637 by per...@carrosses.com: Patch for /trunk/src/google/protobuf/stubs/once.cc http://code.google.com/p/protobuf/issues/detail?id=637 Here is the full patch. Attachments: protobuf-0001-fix-protobufoncetype.patch 2.7 KB -- You received this message because this

[protobuf] Issue 637 in protobuf: Patch for /trunk/src/google/protobuf/stubs/once.cc

2014-05-09 Thread protobuf
Status: New Owner: Labels: Type-Patch New issue 637 by per...@carrosses.com: Patch for /trunk/src/google/protobuf/stubs/once.cc http://code.google.com/p/protobuf/issues/detail?id=637 Specify the right type of once to fix this compilation failure: http://autobuild.buildroot.net/results

[protobuf] Re: Issue 636 in protobuf: Bug in com.google.protobuf.TextFormat.TextGenerator.print()

2014-05-08 Thread protobuf
Updates: Status: Accepted Comment #1 on issue 636 by xiaof...@google.com: Bug in com.google.protobuf.TextFormat.TextGenerator.print() http://code.google.com/p/protobuf/issues/detail?id=636 (No comment was entered for this change.) -- You received this message because this project is

[protobuf] Issue 636 in protobuf: Bug in com.google.protobuf.TextFormat.TextGenerator.print()

2014-05-08 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 636 by adityaki...@gmail.com: Bug in com.google.protobuf.TextFormat.TextGenerator.print() http://code.google.com/p/protobuf/issues/detail?id=636 In TextGenerator.print(...) ... write

[protobuf] Re: Issue 447 in protobuf: No C++11 move constructors

2014-05-06 Thread protobuf
Comment #9 on issue 447 by arnethed...@gmail.com: No C++11 move constructors http://code.google.com/p/protobuf/issues/detail?id=447 Attaching a compiler plugin which adds move construction, assignment and string move assignment to the generated C++ code - to use, simply add --cxx11_out

[protobuf] Re: Issue 447 in protobuf: No C++11 move constructors

2014-05-04 Thread protobuf
Comment #8 on issue 447 by m...@google.com: No C++11 move constructors http://code.google.com/p/protobuf/issues/detail?id=447 Any updates on this? Attached is a patch is that adds a move constructor and assignment operator to the generated messages. Attachments: patch 2.4 KB

[protobuf] Issue 635 in protobuf: Min and max not defined under Windows/Intel C++

2014-05-04 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 635 by dmitrinesteruk: Min and max not defined under Windows/Intel C++ http://code.google.com/p/protobuf/issues/detail?id=635 What steps will reproduce the problem? 1. Try compiling using Intel C++ compiler

[protobuf] Issue 634 in protobuf: Header file path is wrong in generated .cc files for .proto files in inner directories

2014-05-01 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 634 by ajo...@definitionnetworks.com: Header file path is wrong in generated .cc files for .proto files in inner directories http://code.google.com/p/protobuf/issues/detail?id=634 What steps will reproduce

[protobuf] Issue 633 in protobuf: Double encoded as length-delimited wire-type

2014-04-22 Thread protobuf
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 633 by stijnsan...@gmail.com: Double encoded as length-delimited wire-type http://code.google.com/p/protobuf/issues/detail?id=633 What steps will reproduce the problem? 1. Using https://github.com/rethinkdb/rethinkdb

[protobuf] Issue 632 in protobuf: Protocol buffer library fails to build if download directory path contains a space.

2014-04-21 Thread protobuf
Status: New Owner: liuj...@google.com Labels: Type-Defect Priority-Medium New issue 632 by tom.ritc...@gmail.com: Protocol buffer library fails to build if download directory path contains a space. http://code.google.com/p/protobuf/issues/detail?id=632 What steps will reproduce the problem

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

2014-04-21 Thread protobuf
Comment #11 on issue 434 by tom.ritc...@gmail.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 Another xoogler here. Unfortunately convinced my team to use

[protobuf] Re: Issue 631 in protobuf: Fixing issue #641

2014-04-19 Thread protobuf
Comment #1 on issue 631 by omer.d...@gmail.com: Fixing issue #641 http://code.google.com/p/protobuf/issues/detail?id=631 Please close. There's a better patch in #641. -- You received this message because this project is configured to send all issue notifications to this address. Yo

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

2014-04-19 Thread protobuf
Comment #1 on issue 621 by omer.d...@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 I didn't notice you already had a patch. Please pull ASAP. -- You received this message because this proje

[protobuf] Issue 631 in protobuf: Fixing issue #641

2014-04-19 Thread protobuf
Status: New Owner: Labels: Type-Patch New issue 631 by omer.d...@gmail.com: Fixing issue #641 http://code.google.com/p/protobuf/issues/detail?id=631 I surrounded the print statements with parenthesis. Hopefully thats it. Attachments: setup.py.patch 782 bytes -- You received this

[protobuf] Re: Issue 502 in protobuf: protoc generated Java code has numerous javadoc warnings

2014-04-18 Thread protobuf
Comment #4 on issue 502 by jhuxh...@googlemail.com: protoc generated Java code has numerous javadoc warnings http://code.google.com/p/protobuf/issues/detail?id=502 Java 8 javadoc is now creating warnings without explicitly activating them. Fixing them manually isn't worthwhile sinc

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

2014-04-15 Thread protobuf
Comment #7 on issue 630 by kral.voj...@gmail.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 I see. That is what confuse me the difference between attributes with zeros and the bitFields. -- You received this message because this project

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

2014-04-15 Thread protobuf
Comment #6 on issue 630 by xiaof...@google.com: Java: initializing bitFields variables http://code.google.com/p/protobuf/issues/detail?id=630 Re #5: JVM will only set the value to 0 but an integral protobuf field may have a non-zero default value (set by field option [default = 12345

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