aboutsummaryrefslogtreecommitdiffhomepage
path: root/src/python
Commit message (Collapse)AuthorAge
* Merge pull request #13789 from grpc/v1.8.xGravatar Mehrdad Afshari2017-12-14
|\ | | | | Upmerge changes from v1.8.x to master
| * Merge pull request #13786 from kpayson64/fix_python_server_raceGravatar kpayson642017-12-14
| |\ | | | | | | Fixes race condition in Python server shutdown
| | * Fixes race condition in Python server shutdownGravatar Ken Payson2017-12-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When we set the call state to "CANCELLED" after grpc_cancel_all_calls, we would block other start batch operations from happening. The rpc_state for the cancelled call would still be in the server's rpc_states set, but it would never get removed because there were no active batches for the call, and the only place we remove from rpc_states is when a batch completes. It is better to rely on c-core's cancellation. Once a call is cancelled, all subsequent ops on that call will return immediately with a cancellation error. The RLock() change is due to the possibility that _on_call_completed gets invoked immediately when the call has already completed when the rpc_future callback is created.
| * | Reallow out-of-spec metadataGravatar Nathaniel Manista2017-12-14
| |/ | | | | | | | | | | This restore unsupported, de facto behavior that was dropped in 80516e884a8cd03daaa1f4a40d2bb2 but that it turns out a lot of folks have been using.
* | Merge remote-tracking branch 'origin/v1.8.x'Gravatar Mehrdad Afshari2017-12-11
|\|
| * v1.8.0-pre2 is now v1.8.0Gravatar Mehrdad Afshari2017-12-12
| |
| * Add tests for gRPC Python interceptor machineryGravatar Mehrdad Afshari2017-12-12
| |
| * Add gRPC Python client-side interceptor machineryGravatar Mehrdad Afshari2017-12-12
| |
| * Add gRPC Python service-side interceptor machineryGravatar Mehrdad Afshari2017-12-12
| |
* | yapf grpcio_testsGravatar ncteisen2017-12-11
| |
* | yapf-ize grpc_testingGravatar ncteisen2017-12-11
| |
* | yapf-ize grpcio_reflectionGravatar ncteisen2017-12-11
| |
* | yapf-ize grpcio_health_checkingGravatar ncteisen2017-12-11
| |
* | Yapf-ize grpcio/grpc_.pyGravatar ncteisen2017-12-11
| |
| * Refactor: Rename call to response_iterator_callGravatar Mehrdad Afshari2017-12-10
| | | | | | | | Rename call to response_iterator_call file-wide for response-streaming tests.
| * Tests for ServicerContext.abortGravatar Mehrdad Afshari2017-12-10
| |
| * Introduce ServicerContext.abort to abort an RPCGravatar Mehrdad Afshari2017-12-10
| | | | | | | | | | | | | | | | | | | | | | | | gRPC Python required RPCs terminating with non-OK status code to still return a valid response value after calling set_code, even though the response value was not supposed to be communicated to the client, and returning None is considered a programming error. This commit introduces an alternative mechanism to terminate RPCs by calling the `abort` method on `ServicerContext` passed to the handler, which raises an exception and signals to the gRPC runtime to abort the RPC with the specified status code and details.
| * Merge pull request #13688 from nathanielmanistaatgoogle/12531Gravatar Nathaniel Manista2017-12-08
| |\ | | | | | | Elide cygrpc.Operations.
| | * Elide cygrpc.OperationsGravatar Nathaniel Manista2017-12-08
| | |
| * | Merge pull request #13672 from nathanielmanistaatgoogle/12531Gravatar Nathaniel Manista2017-12-08
| |\| | | | | | | Streamline metadata in gRPC Python.
| | * Streamline metadata in gRPC PythonGravatar Nathaniel Manista2017-12-08
| | |
* | | virtual destructor in exec_ctx, remove unneeded flush in grpc_shutdown and ↵Gravatar Yash Tibrewal2017-12-07
| | | | | | | | | | | | remove grpc_exec_ctx from .pxi files in python
| | * Fix Beta API metadata loosenessGravatar Nathaniel Manista2017-12-08
| | |
* | | Upmerge changes from v1.8.x to masterGravatar Mehrdad Afshari2017-12-05
|\| |
| * | Refactor: rename 'e' to 'exception'Gravatar Mehrdad Afshari2017-12-04
| | |
| * | Return UNKNOWN on GenericRpcHandler failureGravatar Mehrdad Afshari2017-12-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * | Merge pull request #13603 from nathanielmanistaatgoogle/credentialsGravatar Nathaniel Manista2017-12-04
| |\| | | | | | | Change client-side credentials' use of gRPC Core.
| * | Merge pull request #13593 from nathanielmanistaatgoogle/12531Gravatar Nathaniel Manista2017-12-04
| |\ \ | | | | | | | | Refactor _plugin_wrapping.
| | | * Change client-side credentials' use of gRPC CoreGravatar Nathaniel Manista2017-12-03
| | | | | | | | | | | | | | | | | | | | | | | | 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.
| | | * Fix some doc string formatting and contentGravatar Nathaniel Manista2017-12-03
| | |/
| | * Refactor _plugin_wrappingGravatar Nathaniel Manista2017-12-01
| | |
| * | Merge pull request #13587 from ↵Gravatar Nathaniel Manista2017-12-01
| |\| | | | | | | | | | | | | nathanielmanistaatgoogle/access-token-auth-metadata-plugin Correct AccessTokenAuthMetadataPlugin name.
| | * Correct AccessTokenAuthMetadataPlugin nameGravatar Nathaniel Manista2017-12-01
| | | | | | | | | | | | It was never itself a "call credentials" of any sort.
* | | Move histogram to test/core/utilGravatar Vijay Pai2017-11-30
| | |
| * | Merge branch 'master' of https://github.com/grpc/grpc into v1.8.xGravatar Nicolas "Pixel" Noble2017-11-30
| |\ \ | |/ / |/| / | |/
* | Merge branch 'master' of https://github.com/grpc/grpc into upmerge-from-v1.7Gravatar Nicolas "Pixel" Noble2017-11-29
|\ \
| | * Avoid unsupported and unintended API self-useGravatar Nathaniel Manista2017-11-28
| | | | | | | | | | | | | | | | | | | | | "Do not make undocumented and unsupported use of one part of an API from within the implementation of another part of the same API" is one of the rules of Abstraction Club. Not sure if it's important enough to be the first two rules, but it's up there.
| | * grpc.CallCredentials doc string correctionGravatar Nathaniel Manista2017-11-28
| | |
| * | Merge pull request #13515 from mehrdada/bump-master-versionGravatar Mehrdad Afshari2017-11-28
| |\ \ | | | | | | | | Bump 1.8.0-dev to 1.9.0-dev
| * \ \ Merge pull request #13491 from vjpai/destackGravatar Vijay Pai2017-11-28
| |\ \ \ | | | | | | | | | | Pop lockfree stack off core implementation
| | | * | Bump 1.8.0-dev to 1.9.0-devGravatar Mehrdad Afshari2017-11-27
| | |/ / | |/| |
| | | * Bump 1.8.0-dev to 1.8.0-pre1Gravatar Mehrdad Afshari2017-11-27
| | |/ | |/|
| * | Update Python dependency to protobuf v3.5.0.post1Gravatar Mehrdad Afshari2017-11-27
| | |
| | * Remove lockfree stack, againGravatar Vijay Pai2017-11-22
| |/
| * Merge pull request #13486 from nathanielmanistaatgoogle/elide-local-fieldGravatar Nathaniel Manista2017-11-22
| |\ | | | | | | Elide local field by directly returning values.
| * \ Merge pull request #13485 from nathanielmanistaatgoogle/constGravatar Nathaniel Manista2017-11-21
| |\ \ | | | | | | | | Add missing const.
| | | * Elide local field by directly returning valuesGravatar Nathaniel Manista2017-11-22
| | |/
| | * Add missing constGravatar Nathaniel Manista2017-11-22
| | |
| * | Merge pull request #13479 from ↵Gravatar Nathaniel Manista2017-11-21
| |\ \ | | | | | | | | | | | | | | | | nathanielmanistaatgoogle/certificate-configuration Avoid abbreviation in Python API.
| | * | Avoid abbreviation in Python APIGravatar Nathaniel Manista2017-11-21
| | |/ | | | | | | | | | | | | I should have requested this during code review of bcf083fa9099e5c919 but it slipped my mind.