- Jun 09, 2015
-
-
Craig Tiller authored
-
Craig Tiller authored
-
- Jun 05, 2015
-
-
Craig Tiller authored
-
Vijay Pai authored
-
Jorge Canizales authored
-
Jorge Canizales authored
-
- Jun 04, 2015
-
-
Jorge Canizales authored
-
Jorge Canizales authored
-
Jorge Canizales authored
-
Jorge Canizales authored
-
Jan Tattermusch authored
-
Jorge Canizales authored
-
Jorge Canizales authored
-
Tim Emiola authored
-
Craig Tiller authored
-
Tim Emiola authored
-
Craig Tiller authored
-
Masood Malekghassemi authored
-
- Jun 03, 2015
-
-
Nicolas "Pixel" Noble authored
-
Yang Gao authored
-
Tim Emiola authored
-
Tim Emiola authored
-
Tim Emiola authored
-
Tim Emiola authored
-
Vijay Pai authored
-
murgatroid99 authored
-
murgatroid99 authored
-
Masood Malekghassemi authored
The previous timeout was short enough that it led to erroneous failures. Fixes #1875.
-
Nicolas "Pixel" Noble authored
That value actually MAY be NULL in some circumstances, and that's not a problem.
-
Jan Tattermusch authored
-
- Jun 02, 2015
-
-
Jorge Canizales authored
-
David Garcia Quintas authored
As a no-op for the time being.
-
vjpai authored
-
Jorge Canizales authored
-
Tim Emiola authored
- stops attempting to verify by catching the CancelledError - instead the test examines the operation state after cancellation, which is equally valid and more stable. Also - simplifies bidi on the server
-
Craig Tiller authored
-
David Garcia Quintas authored
Introduced grpc_byte_buffer_init instead. It's now the user's responsibility to manage memory.
-
Nicolas "Pixel" Noble authored
-
Jan Tattermusch authored
-
- Jun 01, 2015
-
-
Alistair Veitch authored
-