tower-rs / tower-rs/tower-http
Include the actual error message on gRPC failure
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 913
- Forks
- 231
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 8
Description
Feature Request
Motivation
Currently when there is a gRPC error a tracing event is generated at the error level with the generic response failed message. We can see this event in the logs as well. However, the message is not informative and it hides the actual error.
Proposal
We need to modify DefaultOnFailure and GrpcErrorsAsFailures so that the error message and the status code are available in the on_failure() method.
Contributor guide
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 DefaultOnFailure and GrpcErrorsAsFailures entry points named in the issue, and trace how they provide data to on_failure(). Done means the actual error message and status code are available there instead of only the generic response failed message; check the existing gRPC failure behavior while working.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc, rust
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100