Reland "Merge commit '4c51abf12053e3c43a62059c693322ea992b35ce' into main"

This is a reland of commit 98137ddf9a4ca85fcf18ab1b4923fcf46e38748d

It is not tenable to have to fully patch fuchsia.git's //build/secondary/third_party/grpc/BUILD.gn into the main here whenever we need to update the gRPC GI pin and avoid a breaking change so instead we have decided to maintain the copy here in sync with //build/secondary/third_party/grpc/BUILD.gn

Original change's description:
> Merge commit '4c51abf12053e3c43a62059c693322ea992b35ce' into main
>
> Removed Fuchsia specific local patch: templates/BUILD.gn.template and README.Fuchsia
>
> Copied BUILD.gn from https://fuchsia-review.git.corp.google.com/c/fuchsia/+/1151492
>
> https://fuchsia.googlesource.com/third_party/grpc/+/4c51abf12053e3c43a62059c693322ea992b35ce is the head commit of tag/1.48.0-pre1
> Run git diff between this commit and 4c51abf12053e3c43a62059c693322ea992b35ce, the only diff is BUILD.gn.
>
> Note that this change is ONLY used for avoiding breaking change. It is a transition change for upreving gRPC to tag/1.48.0-pre1.
>
> Bug: 377536116
>
> Change-Id: Ie4eefa0f9c2abecf051a856bd885fb6f905b0144
> Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/grpc/+/1151415
> Reviewed-by: Francois Rousseau <frousseau@google.com>

Bug: 377536116
Change-Id: I61e5ac7fede996f9334ee6b397bb086d56cbc00b
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/grpc/+/1157254
Reviewed-by: Francois Rousseau <frousseau@google.com>
10571 files changed
tree: 61849d677f3561532c3e4397687d4cd6c91417ca
  1. .bazelci/
  2. .github/
  3. bazel/
  4. cmake/
  5. doc/
  6. etc/
  7. examples/
  8. include/
  9. spm-core-include/
  10. spm-cpp-include/
  11. src/
  12. summerofcode/
  13. templates/
  14. test/
  15. third_party/
  16. tools/
  17. .bazelignore
  18. .bazelrc
  19. .clang-format
  20. .clang-tidy
  21. .editorconfig
  22. .gitallowed
  23. .gitattributes
  24. .gitignore
  25. .gitmodules
  26. .istanbul.yml
  27. .pylintrc
  28. .pylintrc-examples
  29. .pylintrc-tests
  30. .rspec
  31. .travis.yml
  32. .yapfignore
  33. .yardopts
  34. _metadata.py
  35. AUTHORS
  36. BUILD
  37. BUILD.gn
  38. build_autogenerated.yaml
  39. build_config.rb
  40. build_handwritten.yaml
  41. BUILDING.md
  42. CMakeLists.txt
  43. CODE-OF-CONDUCT.md
  44. composer.json
  45. CONCEPTS.md
  46. config.m4
  47. config.w32
  48. CONTRIBUTING.md
  49. Gemfile
  50. GOVERNANCE.md
  51. gRPC-C++.podspec
  52. gRPC-Core.podspec
  53. gRPC-ProtoRPC.podspec
  54. gRPC-RxLibrary.podspec
  55. grpc.bzl
  56. grpc.def
  57. grpc.gemspec
  58. grpc.gyp
  59. gRPC.podspec
  60. LICENSE
  61. MAINTAINERS.md
  62. Makefile
  63. MANIFEST.md
  64. NOTICE.txt
  65. OWNERS
  66. Package.swift
  67. package.xml
  68. PYTHON-MANIFEST.in
  69. Rakefile
  70. README.md
  71. requirements.bazel.txt
  72. requirements.txt
  73. SECURITY.md
  74. setup.cfg
  75. setup.py
  76. TROUBLESHOOTING.md
  77. WORKSPACE
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.

Join the chat at https://gitter.im/grpc/grpc

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/cpp directory
  • C#: NuGet package Grpc
  • 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
  • Objective-C: Add gRPC-ProtoRPC dependency 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:

LanguageSource
Shared C [core library]src/core
C++src/cpp
Rubysrc/ruby
Pythonsrc/python
PHPsrc/php
C# (core library based)src/csharp
Objective-Csrc/objective-c
LanguageSource repo
Javagrpc-java
Kotlingrpc-kotlin
Gogrpc-go
NodeJSgrpc-node
WebJSgrpc-web
Dartgrpc-dart
.NET (pure C# impl.)grpc-dotnet
Swiftgrpc-swift