Skip to content
Snippets Groups Projects
Select Git revision
  • 013eda440b1e203c06254a161e93156a5f761c3c
  • master default protected
  • arm-aarch-platform
  • arm-platform
  • vjpai-patch-3
  • vjpai-patch-1
  • v1.27.x
  • jtattermusch-patch-2
  • jtattermusch-patch-1
  • update-java-worker-example-in-performance-docs
  • revert-21805-revert-21797-reintroduce_21527
  • revert-21804-tls-credentials-1
  • zhen_cleanup_namecheck
  • revert-21806-revert-21767-revert-21725-revert-21680-cq_ordering
  • vjpai-patch-2
  • revert-21766-tls-credentials-1
  • revert-21640-change_local_tcp_security_level
  • revert-21680-cq_ordering
  • revert-21527-unify_boringssl_deps2
  • revert-20803-grpclb_stabilization
  • fix-kokoro-rvm-key
  • v1.27.0
  • v1.27.0-pre2
  • v1.27.0-pre1
  • v1.26.0
  • v1.26.0-pre1
  • v1.25.0
  • v1.25.0-pre1
  • v1.24.3
  • v1.24.2
  • v1.24.1
  • v1.23.1
  • v1.24.0
  • v1.24.0-pre2
  • v1.24.0-pre1
  • v1.22.1
  • v1.23.0
  • v1.23.0-pre1
  • v1.22.0
  • v1.22.0-pre1
  • v1.21.4
41 results

README.md

Blame
  • user avatar
    Jan Tattermusch authored
    a22a19fd
    History

    Errors and Cancelletion code samples for grpc-ruby

    The examples in this directory show use of grpc errors.

    On the server side, errors are returned from service implementations by raising a certain GRPC::BadStatus exception.

    On the client side, GRPC errors get raised when either:

    • the call completes (unary and client-streaming call types)
    • the response Enumerable is iterated through (server-streaming and bidi call types).

    To run the examples here:

    Start the server:

    > ruby error_examples_server.rb

    Then run the client:

    > ruby error_examples_client.rb