0f1afec5a8
The very non-trivial upgrade of third_party/protobuf to 22.x This PR strives to be as small as possible and many changes that were compatible with protobuf 21.x and didn't have to be merged atomically with the upgrade were already merged. Due to the complexity of the upgrade, this PR wasn't created automatically by a tool, but manually. Subsequent upgraded of third_party/protobuf with our OSS release script should work again once this change is merged. This is best reviewed commit-by-commit, I tried to group changes in logical areas. Notable changes: - the upgrade of third_party/protobuf submodule, the bazel protobuf dependency itself - upgrade of UPB dependency to 22.x (in the past, we used to always upgrade upb to "main", but upb now has release branch as well). UPB needs to be upgraded atomically with protobuf since there's a de-facto circular dependency (new protobuf depends on new upb, which depends on new protobuf for codegen). - some protobuf and upb bazel rules are now aliases, so ` extract_metadata_from_bazel_xml.py` and `gen_upb_api_from_bazel_xml.py` had to be modified to be able to follow aliases and reach the actual aliased targets. - some protobuf public headers were renamed, so especially `src/compiler` needed to be updated to use the new headers. - protobuf and upb now both depend on utf8_range project, so since we bundle upb with grpc in some languages, we now have to bundle utf8_range as well (hence changes in build for python, PHP, objC, cmake etc). - protoc now depends on absl and utf8_range (previously protobuf had absl dependency, but not for the codegen part), so python's make_grpcio_tools.py required partial rewrite to be able to handle those dependencies in the grpcio_tools build. - many updates and fixes required for C++ distribtests (currently they all pass, but we'll probably need to follow up, make protobuf's and grpc's handling of dependencies more aligned and revisit the distribtests) - bunch of other changes mostly due to overhaul of protobuf's and upb's internal build layout. TODOs: - [DONE] make sure IWYU and clang_tidy_code pass - create a list of followups (e.g. work to reenable the few tests I had to disable and to remove workaround I had to use) - [DONE in cl/523706129] figure out problem(s) with internal import --------- Co-authored-by: Craig Tiller <ctiller@google.com> |
||
|---|---|---|
| .bazelci | ||
| .github | ||
| bazel | ||
| cmake | ||
| doc | ||
| etc | ||
| examples | ||
| fuzztest | ||
| include | ||
| spm-core-include | ||
| spm-cpp-include | ||
| src | ||
| summerofcode | ||
| templates | ||
| test | ||
| third_party | ||
| tools | ||
| .bazelignore | ||
| .bazelrc | ||
| .clang-format | ||
| .clang-tidy | ||
| .editorconfig | ||
| .gitallowed | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .istanbul.yml | ||
| .pylintrc | ||
| .pylintrc-examples | ||
| .pylintrc-tests | ||
| .rspec | ||
| .yapfignore | ||
| .yardopts | ||
| AUTHORS | ||
| BUILD | ||
| BUILDING.md | ||
| CMakeLists.txt | ||
| CODE-OF-CONDUCT.md | ||
| CONCEPTS.md | ||
| CONTRIBUTING.md | ||
| GOVERNANCE.md | ||
| Gemfile | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| MANIFEST.md | ||
| Makefile | ||
| NOTICE.txt | ||
| OWNERS | ||
| PYTHON-MANIFEST.in | ||
| Package.swift | ||
| README.md | ||
| Rakefile | ||
| SECURITY.md | ||
| TROUBLESHOOTING.md | ||
| WORKSPACE | ||
| _metadata.py | ||
| build_autogenerated.yaml | ||
| build_config.rb | ||
| build_handwritten.yaml | ||
| composer.json | ||
| config.m4 | ||
| config.w32 | ||
| gRPC-C++.podspec | ||
| gRPC-Core.podspec | ||
| gRPC-ProtoRPC.podspec | ||
| gRPC-RxLibrary.podspec | ||
| gRPC.podspec | ||
| grpc.bzl | ||
| grpc.def | ||
| grpc.gemspec | ||
| grpc.gyp | ||
| package.xml | ||
| requirements.bazel.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
README.md
gRPC – An RPC library and framework
gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere. gRPC enables client and server applications to communicate transparently, and simplifies the building of connected systems.
| Homepage: | grpc.io |
| Mailing List: | grpc-io@googlegroups.com |
To start using gRPC
To maximize usability, gRPC supports the standard method for adding dependencies to a user's chosen language (if there is one). In most languages, the gRPC runtime comes as a package available in a user's language package manager.
For instructions on how to use the language-specific gRPC runtime for a project, please refer to these documents
- C++: follow the instructions under the
src/cppdirectory - C#/.NET: NuGet packages
Grpc.Net.Client,Grpc.AspNetCore.Server - Dart: pub package
grpc - Go:
go get google.golang.org/grpc - Java: Use JARs from Maven Central Repository
- Kotlin: Use JARs from Maven Central Repository
- Node:
npm install @grpc/grpc-js - Objective-C: Add
gRPC-ProtoRPCdependency to podspec - PHP:
pecl install grpc - Python:
pip install grpcio - Ruby:
gem install grpc - WebJS: follow the grpc-web instructions
Per-language quickstart guides and tutorials can be found in the documentation section on the grpc.io website. Code examples are available in the examples directory.
Precompiled bleeding-edge package builds of gRPC master branch's HEAD are
uploaded daily to packages.grpc.io.
To start developing gRPC
Contributions are welcome!
Please read How to contribute which will guide you through the entire workflow of how to build the source code, how to run the tests, and how to contribute changes to the gRPC codebase. The "How to contribute" document also contains info on how the contribution process works and contains best practices for creating contributions.
Troubleshooting
Sometimes things go wrong. Please check out the Troubleshooting guide if you are experiencing issues with gRPC.
Performance
See the Performance dashboard for performance numbers of master branch daily builds.
Concepts
See gRPC Concepts
About This Repository
This repository contains source code for gRPC libraries implemented in multiple languages written on top of a shared C core library src/core.
Libraries in different languages may be in various states of development. We are seeking contributions for all of these libraries:
| Language | Source |
|---|---|
| Shared C [core library] | src/core |
| C++ | src/cpp |
| Ruby | src/ruby |
| Python | src/python |
| PHP | src/php |
| C# (core library based) | src/csharp |
| Objective-C | src/objective-c |
| Language | Source repo |
|---|---|
| Java | grpc-java |
| Kotlin | grpc-kotlin |
| Go | grpc-go |
| NodeJS | grpc-node |
| WebJS | grpc-web |
| Dart | grpc-dart |
| .NET (pure C# impl.) | grpc-dotnet |
| Swift | grpc-swift |