| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
The ideal fix would be to have a tox test command for running the
interop server and client.
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reorganizes the Python code, scraps the current testing
infrastructure, and implements a simple test discovery and run script
based on the standard Python unittest library so we can trust that our
tests are running.
|
|
|
|
|
|
| |
Context management is implemented.
Stub deletion now cancels all RPCs immediately.
|
|
|
|
|
|
|
|
|
| |
For a termination action to properly mark an _End as having stopped it
must clear the _End's _cycle attribute. To be able to do that the
termination action must hold a reference to the _End instance.
Migrating the _termination_action behavior that creates termination
actions into the scope of the _End instance is the best way to afford
the needed instance reference.
|
|\ |
|
| |\ |
|
| | |\
| | | |
| | | | |
Merge release-0_11 into master
|
|\ \ \ \
| | |/ /
| |/| | |
|
| | | | |
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The encoding of the issuer field in this cert is now a PRINTABLESTRING
as opposed to UTF8STRING in the previous server1.pem which was causing
the Go issue.
Fixes #4086.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Warnings will be emitted when trying to import through alpha packages.
|
| | |
| | |
| | |
| | | |
Also uses the .proto files for the service/stub definitions.
|
| | | |
|
|/| |
| | |
| | | |
Add python-dev and python3-dev to prerequisites
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| | |
|
|\ \
| |/
|/| |
Update test for changed core HTTP header handling.
|
|\ \
| | |
| | | |
Update Python release number to 0.11.0b1.
|
| | | |
|
|\ \ \
| | | |
| | | | |
Test coverage for callbacks added to Face futures
|
|\ \ \ \
| | | | |
| | | | | |
Further maintenance of Python dependencies
|
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
This defect was introduced in 9e4d0610ea5e2bb302c. I had thought that
this code was exercised in tests but it is bypassed by the use of
grpc_test.beta.test_utilities.not_really_secure_channel. :-(
|
| |_|/
|/| | |
|
| |/
|/| |
|
|/
|
|
|
| |
These changes probably should have been in 3b0fefb246caf9cf983d8 but
were overlooked.
|
|
|
|
|
| |
The old package directory handling was stale in grpcio's setup.py
command support module and docgen had a typo.
|
| |
|
|\
| |
| | |
Make servers and stubs context managers
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
(1) Move dependency on protobuf from grpcio to grpcio_test. While the
most-commonly-foreseen use case of grpcio makes use of protobuf,
technically protobuf is not strictly needed and there's no actual
in-code relationship between grpcio and protobuf.
(2) Loosen the dependency on protobuf from ==3.0.0a3 to >=3.0.0a3.
(3) Update all references to 0.10.0* to 0.11.0.
(4) Alphabetize the grpcio_test dependencies.
|
|/
|
|
|
|
|
|
|
|
| |
Servers and stubs were context managers in the Alpha API; they may not
need to be in the Beta API but it's easy enough to do, eases migration,
and probably helps some use cases.
For now the stub is given empty __enter__ and __exit__ methods; we can
always come back and implement the actual work of context management in
a later change.
|
|\
| |
| | |
Final beta API cleanup
|
|\ \
| | |
| | | |
The gRPC protocol objects
|
|\ \ \
| | | |
| | | | |
Plumb protocol objects through RPC Framework core
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(1) Renamed the "beta" module "implementations" because it hasn't been
monolithic since "interfaces" was factored out of it a few changes
back.
(2) Moved ChannelConnectivity from grpc.beta.beta to
grpc.beta.interfaces since it is constants that don't depend on the
beta implementation.
(3) Moved the Server interface definition from grpc.beta.beta to
grpc.beta.interfaces since it is an interface.
(4) Dropped the "create_" prefix from "create_<...>_channel" functions
to better match the other creation functions throughout the codebase.
|
| |/ |
|
| | |
|
|/ |
|
| |
|
|\
| |
| | |
Respond with UNIMPLEMENTED when a requested method is not found
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
It may seem weird that code and details would travel along two paths
now instead of one but it makes sense after considering that sometimes
the code and details are application data from the remote application
and sometimes they are transport data from the transport between the
local and remote applications.
|
| | |
|
|/ |
|