| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
Upgrade yapf version to 0.20.0 and reformat Python files.
|
| |\
| |
| | |
Reform cygrpc.OperationTag and cygrpc.Event.
|
| |\ \
| | |
| | |
| | | |
Upmerge v1.8.3 into master
|
| | |/
| |
| |
| |
| |
| | |
Rather than single classes they are now broken up into class families
with each class containing only those fields and methods that are
needed in the context in which the class is used.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
It is now a family of classes conforming to an interface rather than a
single class no single instance of which makes use of all behavior
scoped to the class.
It also now only uses gRPC Core memory for the time of a single batch
rather than for the entire lifetime of the instance.
|
| | | |
|
| |\ \
| |/
|/| |
Disable so_reuseport for Python tests
|
| | | |
|
| |/
|
|
|
|
| |
This restore unsupported, de facto behavior that was dropped in
80516e884a8cd03daaa1f4a40d2bb2 but that it turns out a lot of folks
have been using.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Rename call to response_iterator_call file-wide for response-streaming tests.
|
| | |
|
| |\
| |
| | |
Elide cygrpc.Operations.
|
| | | |
|
| |\|
| |
| | |
Streamline metadata in gRPC Python.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
A GenericRpcHandler registered on a gRPC Server is not supposed to raise
an exception and if it does so it is considered a programming defect.
However, gRPC is supposed to respond to the client with an UNKNOWN
status code. Previously, this situation was left unhandled and the
client ended up receiving a response with CANCELLED status code.
This commit fixes the issue https://github.com/grpc/grpc/issues/13629.
|
| |
|
|
|
|
| |
Rather than allocating gRPC Core memory when instantiated and
retaining it until deleted, gRPC Python's credentials objects now
offer methods to create gRPC Core structures on demand.
|
| |
|
|
| |
It was never itself a "call credentials" of any sort.
|
| |\
| |
| |
| |
| | |
nathanielmanistaatgoogle/certificate-configuration
Avoid abbreviation in Python API.
|
| | |
| |
| |
| |
| | |
I should have requested this during code review of bcf083fa9099e5c919
but it slipped my mind.
|
| |\ \
| |/
|/| |
Require port and server_port interop flags.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, a secure server is configured with SSL credentials during
initialization, and those credentials will be used for the lifetime of
the server. If the user wants the server to use new credentials, the
user has to restart the server, resulting in server downtime. This
change enables the user to optionally configure the server with a
"certificiate config fetcher," such that on every new client
connection, the server will call the config fetcher before performing
the handshake, allowing the user application to optionally specify new
certificate configuration for the server to use (the fetcher can
return a "no change" and the server continues to use its current
certificate configuration).
|
| |/
|
|
| |
Also sort arguments to ArgumentParser.add_argument in idiomatic order.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
Beta code elements are not generated at all in _pb2_grpc.py files.
This duplicates a lot of the in-test code generation done in
_split_definitions_test. In a future clean-up we may want to
deduplicate the common behavior, put it in a module available to all
other tests, and do all of our testing of generated code with in-test
code generation.
|
| |\
| |
| | |
Overhaul protoc_plugins._split_definitions_test.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We were mistaken before when we were testing _pb2.py files being
generated in one directory and _pb2_grpc.py files being generated in
another directory. Sure, that was a thing our code generator could do,
but because of the way paths and packages work in Python it wasn't a
realistic use case for actual users.
This test now tests _pb2.py files and _pb2_grpc.py files being
generated either together or independently of one another, and if
independently, in either order. Looking forward to an eventual
py_grpc_library Bazel rule, that's what actually matters.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Move it out of the "unit" package, as it's not itself a unit test.
- Suffix the test class with "Test" as we do with every other subclass
of unittest.TestCase.
- Add a larger-than-we'll-need-any-time-soon maxDiff so that failures
are fully described.
- Relax the assertion from assertListEqual to assertSequenceEqual
since we don't actually care whether or not the sequences being
compared are list instances.
- Change the order of the assertions arguments to match the
"<expected>, <actual>" convention used in our assert*Equal calls
elsewhere throughout the test corpus.
- Internal implementation simplifications.
|
| | |
| |
| |
| |
| |
| |
| | |
Were this not done these would break when the default behavior of gRPC
Python Protoc Plug-In is changed to be the put-gRPC-code-elements-only-
in-_pb2_grpc.py-files behavior that currently happens only when the
grpc_2_0 flag is passed.
|
| |/
|
|
|
|
| |
I wrote these in the course of a bug hunt. I haven't yet caught and
fixed the bug, but that's no reason not to check in perfectly good
tests. :-)
|
| |\
| |
| | |
gRPC Python test infrastructure.
|
| | |
| |
| |
| | |
(The server-related third part of it.)
|
| |/ |
|
| |
|
|
| |
(The channel-related second part of it.)
|
| |
|
|
| |
(The time-related first part of it, anyway.)
|
| | |
|
| | |
|
| | |
|
| |\ |
|
| | | |
|
| |\ \
| | |
| | | |
Update Python interop tests to use google-auth package
|
| | | |
| | |
| | |
| | |
| | | |
The oauth2client test dependency is still needed as it used by
the beta API unit tests.
|
| |/ / |
|
| |/ |
|
| |\ |
|
| | | |
|
Mehrdad Afshari
Nathaniel Manista
Mehrdad Afshari
kpayson64
Giang Nguyen
Jan Tattermusch
murgatroid99
yang-g
Nicolas "Pixel" Noble