Top-level messages may be broken into multiple pieces and streamed if
they are too long. Keep pulling them from the stream until we've got to
the desired length.
Add `grpc::BinderServerCredentials()` and other related functionalities for the server to listen to binder transactions through a phony "binder port".
The APIs are temporarily placed in internal headers until the corresponding gRFC is merged.
* Remove iterator interface from LBPolicy Metadata
Trying to clear the way to think about how metadata is handled in core.
Right now this interface is only used for tests, so a single method that
does what's needed for that (and marked TestOnly) is provided for now.
In the future we'll certainly likely need API to access metadata from
load balancing policies. However, it seems likely that we'll want to
encourage access via lookup-by-key rather than lookup-by-iteration, and
so it seems likely we'll want to expose interfaces phrased in those
terms.
In the meantime, this change localizes some complexity to make it easier
to transition to new internal API's.
* mdcleanup
* [csharp net472] Fix error loading library grpc_csharp_ext.x64.dll on Windows with charset on non ANSI encoding. Example library path: C:\Program Files (x86)\тест\grpc_csharp_ext.x64.dll
* cleanup
* Change charset to Unicode
Co-authored-by: Jan Tattermusch <jtattermusch@google.com>
Add `%(NuGetPackageId)` as is standard procedure for nuget package-provided assets,
so that other MSBuild targets can act on items contributed by Grpc.Core as needed, for
example, in Pack scenarios.
Fixes#26724
Java side implementation does not use header, so we need
AIBinder_Class_disableInterfaceTokenHeader to disable header.
The weak symbol will be resolved when the libbinder_ndk.so on device is
new enough. Otherwise, our transport implementation will keep using
header.
After SDK and NDK that support API level 32 get released, we will remove
this workaround and specify correct minSDKVersion in AndroidManifest
* Add Python 3.10.0rc1 binary wheels
* Drop Python 3.5 artifacts
* Document the drop of 3.5
* Fix the wrong pip pointer
* Update manylinux2014 to a newer version, remove 3.5 distribtest
* Update manylinux aarch64 to see if the absl error go away
* Use the preferred alias
* Allow different wheel library to produce different tag order
* Remove unused shell var and log produced wheels
* Use copy instead of move
* Make bash happy about the wildcard
* Upgrade the debian image to use 3.5+ Python
* Polish the comments for the Dockerfiles
* fix retry code to fail batches instead of creating attempt if previously cancelled from surface
* add xDS end2end tests covering the FI use-case that triggered the bug
* fix memory leak