Google Git
Sign in
fuchsia/third_party/grpc/afe5f6d2a4e31ded8667af0268ed570bf24a7a8c
commit
afe5f6d2a4e31ded8667af0268ed570bf24a7a8c
[log]
author
Craig Tiller <ctiller@google.com>
Fri Oct 27 00:50:10 2023 -0700
committer
GitHub <noreply@github.com>
Fri Oct 27 00:50:10 2023 -0700
tree
7335f12c5b73f2bafc70967632b8130c4afbc563
parent
942e2b1dfd8207dd43608ad44d65b0b18a0df970 [diff]
[chttp2] Fix bug in timeout encoding (#34751)

Just the right combination of timeout values could lead to a large
amount of growth in the timeout cache, leading to high memory usage and
high cpu utilization on the client attempting that encoding.

Fix: cap the number of cached timeout values we'll consider to a very
small number (I'm choosing five).

Add a fuzzer that ensures that we're actually respecting the limits of
inaccuracy we're imposing upon ourselves.

---------

Co-authored-by: ctiller <ctiller@users.noreply.github.com>
6 files changed
tree: 7335f12c5b73f2bafc70967632b8130c4afbc563
  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. BUILD
  41. build_autogenerated.yaml
  42. build_config.rb
  43. build_handwritten.yaml
  44. BUILDING.md
  45. CMakeLists.txt
  46. CODE-OF-CONDUCT.md
  47. composer.json
  48. CONCEPTS.md
  49. config.m4
  50. config.w32
  51. CONTRIBUTING.md
  52. Gemfile
  53. GOVERNANCE.md
  54. gRPC-C++.podspec
  55. gRPC-Core.podspec
  56. gRPC-ProtoRPC.podspec
  57. gRPC-RxLibrary.podspec
  58. grpc.bzl
  59. grpc.def
  60. grpc.gemspec
  61. grpc.gyp
  62. gRPC.podspec
  63. LICENSE
  64. MAINTAINERS.md
  65. Makefile
  66. MANIFEST.md
  67. NOTICE.txt
  68. OWNERS
  69. Package.swift
  70. package.xml
  71. PYTHON-MANIFEST.in
  72. Rakefile
  73. README.md
  74. requirements.bazel.txt
  75. requirements.txt
  76. SECURITY.md
  77. setup.cfg
  78. setup.py
  79. TROUBLESHOOTING.md
  80. 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