Google Git
Sign in
fuchsia / third_party / grpc / 14ac6891c00bb96e967c2f671fa5fc1a250c1be7
commit14ac6891c00bb96e967c2f671fa5fc1a250c1be7[log] [tgz]
authorEugene Ostroukhov <eostroukhov@google.com>Tue May 09 13:54:10 2023 -0700
committerGitHub <noreply@github.com>Tue May 09 13:54:10 2023 -0700
tree63ab46d5710c98aef51ae9434137c5583d807c56
parent06233b9e98f810abcee758dcd2d736d20e0fa4ca [diff]
[infra] Backport: Ensure compatibility with the new custom kokoro win2019 image (#32649) (#33052)

Fix incompatibilities identified when running adhoc runs on the new
custom win2019 image.
After merging this, it should be possible to switch to the new image
without breaking any tests.

- for most fixes I added a comment that explains why they're necessary.
- the new image won't have VS2015 installed, so I'm switching the protoc
artifact build to VS2017

This PR will need to be backported to older release branches to ensure
the windows tests continue working on those branches as well (IMHO I
haven't made any changes that would be difficult to backport and I tried
to keeps the diff as small as possible to avoid issues when
backporting).

After we switch to the new image (and all the windows tests are green),
we can incrementally move the builds that are still using VS2017 to
VS2019.

---------

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