Migrate the unknown-field text-format conformance tests to gtest.
This moves the "Unknown Fields" block of the legacy TextFormatConformanceTestSuiteImpl::RunAllTests() and its RunValidUnknownTextFormatTest() helper into the gtest-based text-format conformance suite (:text_conformance_tests / cpp_text_test):
- ScalarUnknownFields, MessageUnknownFields, GroupUnknownFields, RepeatedUnknownFields, each with its _Drop leg (unknown fields dropped from the text output) and its _Print leg (print_unknown_fields, the fields come back by number) -> text_unknown_field_test.cc, run over the proto3-style message types like the legacy dispatch did (TestAllTypesProto3 in its proto3 and editions flavours).
The payloads are serializations of UnknownToTestAllTypes built inline in each test exactly as before (including the RepeatedUnknownFields payload still carrying the group of the preceding test, which the legacy code never cleared), and the testee's text output is decoded as that type via ParsedPayloadAs(), reproducing the legacy SetPrototypeMessageForCompare() comparison. The tests keep their binary input, RECOMMENDED level and TEXT_FORMAT_TEST category (OverrideTestCategory()).
16 requests move; the test names and request bytes are byte-identical to the legacy ones (migration:request_golden_test is unchanged and passing), and the legacy suite no longer sends them. No failure-list changes: the entries for these tests in text_format_failure_list_java.txt and text_format_failure_list_php.txt, and in the google3-only lists of //net/proto2/contrib/dynamicproto/conformance (text_format_conformance_failures.txt), //javascript/apps/jspb/conformance (text_format_failure_list.txt) and //third_party/golang/protobuf/v2/internal/conformance (failing_tests_text_format.txt), still match because the gtest suite emits the same "TEXT_FORMAT output we received from test was unparseable.", "Failed to parse input or produce output." and "Output was not equivalent to reference message: deleted: ..." messages (verified by running those conformance tests).
RunValidUnknownTextFormatTest() and its declaration are deleted from text_format_conformance_suite.{h,cc}; the reserved-field and map blocks of RunAllTests() are untouched.
Priorities (b/564550230): TextUnknownFieldTest overrides DefaultPriority() to kP3 so the legacy RECOMMENDED tests keep that level. Test names and failure lists are unaffected (kP3 still prints as Recommended, kP0..kP2 as Required).
PiperOrigin-RevId: 984317691
Copyright 2008 Google LLC
Protocol Buffers (a.k.a., protobuf) are Google's language-neutral, platform-neutral, extensible mechanism for serializing structured data. You can learn more about it in protobuf's documentation.
This README file contains protobuf installation instructions. To install protobuf, you need to install the protocol compiler (used to compile .proto files) and the protobuf runtime for your chosen programming language.
Most users will find working from supported releases to be the easiest path.
If you choose to work from the head revision of the main branch your build will occasionally be broken by source-incompatible changes and insufficiently-tested (and therefore broken) behavior.
If you are using C++ or otherwise need to build protobuf from source as a part of your project, you should pin to a release commit on a release branch.
This is because even release branches can experience some instability in between release commits.
Protobuf supports Bzlmod with Bazel 8 +. Users should specify a dependency on protobuf in their MODULE.bazel file as follows.
bazel_dep(name = "protobuf", version = <VERSION>)
Users can optionally override the repo name, such as for compatibility with WORKSPACE.
bazel_dep(name = "protobuf", version = <VERSION>, repo_name = "com_google_protobuf")
Users can also add the following to their legacy WORKSPACE file.
Note that with the release of 30.x there are a few more load statements to properly set up rules_java and rules_python.
http_archive(
name = "com_google_protobuf",
strip_prefix = "protobuf-VERSION",
sha256 = ...,
url = ...,
)
load("@com_google_protobuf//:protobuf_deps.bzl", "protobuf_deps")
protobuf_deps()
load("@rules_java//java:rules_java_deps.bzl", "rules_java_dependencies")
rules_java_dependencies()
load("@rules_java//java:repositories.bzl", "rules_java_toolchains")
rules_java_toolchains()
load("@rules_python//python:repositories.bzl", "py_repositories")
py_repositories()
The protobuf compiler is written in C++. If you are using C++, please follow the C++ Installation Instructions to install protoc along with the C++ runtime.
For non-C++ users, the simplest way to install the protocol compiler is to download a pre-built binary from our GitHub release page.
In the downloads section of each release, you can find pre-built binaries in zip packages: protoc-$VERSION-$PLATFORM.zip. It contains the protoc binary as well as a set of standard .proto files distributed along with protobuf.
If you are looking for an old version that is not available in the release page, check out the Maven repository.
These pre-built binaries are only provided for released versions. If you want to use the github main version at HEAD, or you need to modify protobuf code, or you are using C++, it's recommended to build your own protoc binary from source.
If you would like to build protoc binary from source, see the C++ Installation Instructions.
Protobuf supports several different programming languages. For each programming language, you can find instructions in the corresponding source directory about how to install protobuf runtime for that specific language:
| Language | Source |
|---|---|
| C++ (include C++ runtime and protoc) | src |
| Java | java |
| Python | python |
| Objective-C | objectivec |
| C# | csharp |
| Ruby | ruby |
| Go | protocolbuffers/protobuf-go |
| PHP | php |
| Dart | dart-lang/protobuf |
| JavaScript | protocolbuffers/protobuf-javascript |
The best way to learn how to use protobuf is to follow the tutorials in our developer guide.
If you want to learn from code examples, take a look at the examples in the examples directory.
The complete documentation is available at the Protocol Buffers doc site.
Read about our version support policy to stay current on support timeframes for the language libraries.
To be alerted to upcoming changes in Protocol Buffers and connect with protobuf developers and users, join the Google Group.