Google Git
Sign in
fuchsia / third_party / grpc / HEAD
commit238f990024610534849f5b461c1951807d470622[log] [tgz]
authorJoshua Seaton <joshuaseaton@google.com>Fri Feb 07 18:15:03 2025 -0800
committerJoshua Seaton <joshuaseaton@google.com>Fri Feb 07 18:20:02 2025 -0800
treeac658a098f05251dbb156381a1aa2f6874a8709a
parent141e95f1828e56750ff51c8784739a5c73242a36 [diff]
Merge to v1.65.0

Merge commit created by
```
git merge -X theirs 45479fda2a083c4e46310b9bb6e45e625e381269
```
and then amending to include a copy of the BUILD.gn file generated in
https://fxrev.dev/1201685.

This roll is a blocker to the boringssl roll and v1.65.0 was chosen as
that was the first version tag that removed the code that the new
boringssl version does not like.

Bug: 339028859
Change-Id: Icf475f2a76a63732237900963f5710361530bd2b
Reviewed-on: https://fuchsia-review.googlesource.com/c/third_party/grpc/+/1201532
Reviewed-by: Anivia Li <aniviali@google.com>
6371 files changed
tree: ac658a098f05251dbb156381a1aa2f6874a8709a
  1. .bazelci/
  2. .github/
  3. bazel/
  4. cmake/
  5. doc/
  6. etc/
  7. examples/
  8. fuzztest/
  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.gn
  43. build_autogenerated.yaml
  44. build_config.rb
  45. build_handwritten.yaml
  46. BUILDING.md
  47. CMakeLists.txt
  48. CODE-OF-CONDUCT.md
  49. composer.json
  50. CONCEPTS.md
  51. config.m4
  52. config.w32
  53. CONTRIBUTING.md
  54. CONTRIBUTING_STEPS.md
  55. Gemfile
  56. GOVERNANCE.md
  57. gRPC-C++.podspec
  58. gRPC-Core.podspec
  59. gRPC-ProtoRPC.podspec
  60. gRPC-RxLibrary.podspec
  61. grpc.bzl
  62. grpc.def
  63. grpc.gemspec
  64. grpc.gyp
  65. gRPC.podspec
  66. LICENSE
  67. MAINTAINERS.md
  68. Makefile
  69. MANIFEST.md
  70. NOTICE.txt
  71. Package.swift
  72. package.xml
  73. PYTHON-MANIFEST.in
  74. Rakefile
  75. README.md
  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