Skip to content
Snippets Groups Projects
  1. Mar 31, 2016
  2. Mar 09, 2016
  3. Feb 19, 2016
  4. Feb 05, 2016
  5. Feb 04, 2016
  6. Jan 14, 2016
  7. Jan 07, 2016
  8. Dec 16, 2015
  9. Dec 11, 2015
  10. Dec 04, 2015
  11. Nov 11, 2015
  12. Nov 09, 2015
  13. Oct 28, 2015
  14. Oct 08, 2015
  15. Sep 26, 2015
  16. Sep 01, 2015
  17. Aug 31, 2015
  18. Aug 20, 2015
  19. Aug 17, 2015
  20. Aug 14, 2015
    • Tim Emiola's avatar
      Add a health checker service implementation. · 975d0cb0
      Tim Emiola authored
      - adds the code-generated health service classes to the pb along with
        a README explaining how to regenerate the generated code
      
      - adds an implementation of the Health Checker Service along with unit
        tests and an integration test
      
      Also:
      - adds a pb folder
        : in a follow-up PR, all ruby pbs + generated code will be moved to it
      975d0cb0
    • Tim Emiola's avatar
      Adds the ruby timeout interop test. · cdb7cccc
      Tim Emiola authored
      Corrects some other issues
      
      - fixes status return when calls fail by always returning the status
      
      - resolves bidi_call client's failure to return an exception on bad
        status by swapping the wait for status to the read thread
      
        * this also improves the cancel_after_first_response test
      
      Also
      
      - adds a unit test that verifies that a bidi call will time out.
      cdb7cccc
    • Tim Emiola's avatar
      Breaks API - switches timeout to a keyword arg. · 49b7650e
      Tim Emiola authored
      - timeout has been a default arg till now
      
      - this switches it to a keyword arg with the same behavior
      
      - in addition, it adds deadline as distinct keyword arg, allowing users
        the choice of the idiomatic(timeout) or the aligned(deadline)
      49b7650e
  21. Aug 12, 2015
  22. Aug 11, 2015
  23. Jul 19, 2015
  24. Jun 17, 2015
  25. May 23, 2015
  26. May 20, 2015
  27. May 17, 2015
    • Craig Tiller's avatar
      Ensure that there's always a poller for completion · 09600be0
      Craig Tiller authored
      The C core uses completion_queue_next as a directive that progress should be made on requests bound to that cq.
      If nobody is polling for completion, then a deadlock can occur (client needs to do work, but we're blocked waiting for the server).
      There is no scope for this to occur using the idiomatic layers (as far as I can tell), but these low level tests need to be massaged.
      09600be0
  28. May 12, 2015
Loading