Protocol Buffers

Ack, I found the bug, it was just a bad include path in the makefile. SIGH. On Friday, March 14, 2025

It looks like CMake is trying to link against a different Abseil installation from the one you built.

Regarding the subject of creating my own data types, I discovered that I can use FieldOptions and

You can view the release and complete release notes on GitHub. If you experience any issues with the

Clarification that this version actually includes breaking changes to C++, Objective-C, and Python.

After further debugging, I wonder if the cause might be the fact that this line in the protobuf

This version includes breaking changes to C++, Objective-C, Python, Rust: [C++] Remove deprecated

Hello all. I have read the language guide and tutorial for the language in my use case (C#). So far,

It was a version mismatch. The issue thread https://github.com/bazelbuild/rules_scala/issues/1647

Dear Protobuf Community, I am trying to build the Protobuf Python package (version 3.21.12) from

Now on to linking.... 98 independent absl static libs? Really? Would it not be possible to simply

Poison Java gencode We are patching a change into the 25.x branch that will poison Java gencode that

This version includes breaking changes to C++, Objective-C, Python, Rust: [C++] Remove deprecated

According to Application Note: Field Presence | Protocol Buffers Documentation singular messages are

Hi, I edited the environment variables via Control Panel before Matlab was running. In Matlab command

You can view the release and complete release notes on GitHub. If you experience any issues with the

If you are using Proto3 and find the has-bit even a little bit useful, you should go ahead and use

The code paths have all been deleted. I think that's about as official as you can get. True that.

This does seem to be the issue. I found two different protoc binaries in the bazel cache of my Envoy

You can view the release and complete release notes on GitHub. If you experience any issues with the

I think the updates for this account should not be surprised, by anyone, if ever it does not deserve

Hi all, I discovered today that the proto generator for Dart does not support protobuf editions. This

Thanks for replying and sorry for the late response. We didn't see any occurrences of “3.21” in “

This change should be released with our next quarterly release in early Q1. See https://protobuf.dev/

New Opaque API for Go Back in March 2020, we released the google.golang.org/protobuf module, a major

You can find the latest protoc release in our github releases page (currently v29.2). Note that for

On Fri, Dec 20, 2024 at 1:07 AM 'Mikihito Matsuura' via Protocol Buffers <protobuf@

You can view the release and complete release notes on GitHub. If you experience any issues with the

Hi, I think this shall have gathered all the information: https://stackoverflow.com/questions/

I think this is only happening in the main branch right? There's a fix pending for that https://