Google Git
Sign in
fuchsia/third_party/grpc/refs/heads/upstream/test_748704078
commit
3d0b816c5fd08899b2cb1e8a0f3bbe9805065f75
[log]
author
Craig Tiller <ctiller@google.com>
Thu Apr 17 09:20:35 2025 -0700
committer
Copybara-Service <copybara-worker@google.com>
Thu Apr 17 09:43:49 2025 -0700
tree
7d3707d9e4c6065277e346d841b7835f896b249a
parent
c515ee001252880d85348d8cf87c18cfe31f1efb [diff]
[export] Split CoreConfiguration builders into two buckets: ephemeral and persistent.

We use builders for a variety of tasks - sometimes for testing, sometimes for adapting gRPC to novel environments, sometimes for once off special tasks early in a process lifetime.

Treating these as the same thing has started leading to some problems, so here I introduce a reset-proof registration for a subset of these tasks.

I'll be using this to register chaotic-good into the EndpointTransport registry so that it doesn't need to join the usual core configuration chain (and accidentally pull in protobuf to core).

----
DO NOT SUBMIT. This PR is for testing purposes only. [cl/748704078](http://cl/748704078)

PiperOrigin-RevId: 748704078
31 files changed
tree: 7d3707d9e4c6065277e346d841b7835f896b249a
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. bazel/
  5. cmake/
  6. doc/
  7. etc/
  8. examples/
  9. include/
  10. spm-core-include/
  11. spm-cpp-include/
  12. src/
  13. summerofcode/
  14. templates/
  15. test/
  16. third_party/
  17. tools/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-tidy
  23. .dockerignore
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitallowed
  27. .gitattributes
  28. .gitignore
  29. .gitmodules
  30. .istanbul.yml
  31. .pylintrc
  32. .pylintrc-examples
  33. .pylintrc-tests
  34. .rspec
  35. .yapfignore
  36. .yardopts
  37. _metadata.py
  38. AUTHORS
  39. black.toml
  40. BoringSSL-Package.swift
  41. BUILD
  42. build_autogenerated.yaml
  43. build_config.rb
  44. build_handwritten.yaml
  45. BUILDING.md
  46. CMakeLists.txt
  47. CODE-OF-CONDUCT.md
  48. composer.json
  49. CONCEPTS.md
  50. config.m4
  51. config.w32
  52. CONTRIBUTING.md
  53. CONTRIBUTING_STEPS.md
  54. Gemfile
  55. GOVERNANCE.md
  56. gRPC-C++.podspec
  57. gRPC-Core.podspec
  58. gRPC-ProtoRPC.podspec
  59. gRPC-RxLibrary.podspec
  60. grpc.bzl
  61. grpc.def
  62. grpc.gemspec
  63. gRPC.podspec
  64. LICENSE
  65. MAINTAINERS.md
  66. Makefile
  67. MANIFEST.md
  68. MODULE.bazel
  69. NOTICE.txt
  70. Package.swift
  71. package.xml
  72. PYTHON-MANIFEST.in
  73. Rakefile
  74. README.md
  75. requirements.bazel.lock
  76. requirements.bazel.txt
  77. requirements.txt
  78. SECURITY.md
  79. setup.cfg
  80. setup.py
  81. TROUBLESHOOTING.md
  82. 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#/.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-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