2ee2c91c92
* Reland x2: Make GetDefaultEventEngine return a shared_ptr * remove thread leak from NativeDNSResolver This is not going to work for resolvers that support cancellation. * give resolvers bounded lifetimes Some resolver own EventEngines. EventEngines cannot run off the end of the process since they have unjoined threads (problematic in a small set of environments). This gives resolvers bounded lifetimes, and allows replacement of resolvers without ASAN issues of deleting resolvers in active use (occurs in tests). * fix * fix windows * fix surface init test * fix * sanitize * use after move * the test must wait for the callback to be destroyed * windows fix: delete the resolver on iomgr shutdown, not before * Make TimerManager threads non-joinable On gRPC shutdown, any unjoined TimerManager threads will cause TSAN to detect thread leaks. This fix resolves issues I saw in end2end test shutdown in another PR, where a single timer manager thread was always alive after the test ended. The long-term solution is to integrate the new ThreadPool here, but this unblocks me for now. * backport fix * fix * shared_ptr<EventEngine> in EventEngine benchmarks |
||
|---|---|---|
| .bazelci | ||
| .github | ||
| bazel | ||
| cmake | ||
| doc | ||
| etc | ||
| examples | ||
| 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 | ||
| .travis.yml | ||
| .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#: 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-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 |