Exception handling?
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 160
- Forks
- 14
- Avg merge
- 6d 11h
- Merged PRs (30d)
- 2
Description
Thank you for this light-weight alternative to grpc. I hope to be able to use it in production soon.
But first I need to ask you about exception handling. I don’t see anything mentioned in the Readme, and I find no uses of rescue in the examples/ folder. But when trying this gem out, I ended up getting a lot of GrpcKit::Session::ClientSession::ConnectionClosing exceptions. I am not sure if they are caused by the client session becoming “too old”, or if the client has gotten itself into a bad state, or something else.
Any help (and/or documentation) would be appreciated.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README, the examples/ folder, and the reported GrpcKit::Session::ClientSession::ConnectionClosing exception. Trace how exception handling is described or demonstrated, then document what causes this exception and how users should handle it. Done means the README or related documentation answers the reported production-use question.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100