| Commit message (Collapse) | Author | Age |
... | |
| |/|
|/| | |
|
| | |\
| | | |
| | | | |
Use unique namespace for each python protoc test
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Using the same namespace results in errors when using the c-extension
version of protobuf due to name collisions
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Using the same namespace results in errors when using the c-extension
version of protobuf due to name collisions
|
| | | | |
|
| | |\ \
| | | | |
| | | | | |
Disable libuv core changes in Node library and bump version number
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is for compatibility with IPv6-only environments; see the Google
bug b/32531998.
Note that InteropClient.cs and http2_client.cc don't appear to be tested
by our internal branch, but I've included them for consistency.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This brings gRPC Python into conformance with the recommendation in
https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md.
|
| |/ / |
|
| |/ |
|
| | |
|
| |\
| | |
| | | |
Bump version to 1.1.1
|
| | | |
|
|\ \ \ |
|
| | |/ |
|
| | | |
|
| | | |
|
|/ / |
|
|/ |
|
|\
| |
| |
| |
| | |
soltanmm-google/if-you-rely-only-on-yourself-fewer-things-might-go-wrong-but-fewer-things-might-go-right
Don't leak Py exceptions without calling gRPC core
|
| | |
|
|\ \
| |/
|/|
| |
| | |
soltanmm-google/as-filthy-rich-as-our-cabinet-secretaries
Add __richcmp__ to cygrpc.Timespec
|
|\ \
| | |
| | | |
Fix grpc._server._Context.time_remaining.
|
| |/
|/| |
|
| |
| |
| |
| | |
A weak test is included; proper test coverage will come later.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The test now expects to receive StatusCode.INTERNAL when it receives a
RST_STREAM from the server in order to comply with
https://github.com/grpc/grpc/blob/master/doc/PROTOCOL-HTTP2.md
Also added wait for ready behavior on the client channel.
|
|/
|
|
|
| |
This should have been included in dd52a31337616fe935f79debfe5d56c6d73a
but was missed because it falsely passes almost all of the time.
|
| |
|
|
|
|
|
| |
The clients now block until the channel is in the READY state. This
fixes some test flakiness issues we have had.
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Manual resolution:
- New test added in src/python/grpcio_test/tests/tests.json
- Timeout-related edits resolved in tools/run_tests/run_tests.py
Manual changes:
- Pass request iterator rather than request sequence in
_reflection_servicer_test.py
|
| |
| |
| |
| |
| | |
It's been confusing that these tests have been called "interop" but
are not actually tests of interoperation.
|
| |
| |
| |
| |
| | |
Added tests for detecting invocation time defects arising out of the
runtime.
|
| |
| |
| |
| |
| | |
Cast iterables into iterators for stream based compression, empty
message, and metadata tests.
|
| |\
| | |
| | | |
Drop use of Exception.message in metadata test.
|
|\ \ \
| | | |
| | | | |
v1.0.x manual upmerge
|
| | | |
| | | |
| | | |
| | | | |
Documentation for the new tests can be found https://github.com/grpc/grpc/blob/master/doc/negative-http2-interop-test-descriptions.md
|
| | | |
| | | |
| | | |
| | | | |
Add a comma delimiter for "_invalid_metadata_test.InvalidMetadataTest".
|
| | |/
| | |
| | |
| | |
| | | |
Apparently Exception.message was introduced in Python 2.5 and
deprecated almost immediately afterward in Python 2.6.
|
|/| |
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Manual changes:
- Fixed use of Exception.message in _invalid_metadata_test.py
- Fixed merge of one_failed_as_unavailable in rpc_server_spec.rb
- Added "set -e" to generate_build_additions.sh
|
| |\
| | |
| | | |
Add check on return value from start_client_batch
|
| | | |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Revert "Add configurable exit grace periods and shutdown handlers"
|
| | |\ \
| | | | |
| | | | | |
Interop fixes.
|
| | |\ \ \
| | | |_|/
| | |/| |
| | | | |
| | | | | |
nathanielmanistaatgoogle/channel_ready_future_tests-v1.0.x
Channel ready future test tweaks.
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ /
| | | |
| | | |
| | | |
| | | | |
Setuptools was updated and our hacky namespace-package-chickens came
back to roost. This removes the unsupported namespace package hacks.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Setuptools was updated and our hacky namespace-package-chickens came
back to roost. This removes the unsupported namespace package hacks.
|