-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle error status returns instead of timing out #54
Comments
I've recreated these by sending in invalid content-types from the grpc client, and then tracing things to honeycomb.
Specifically the issue here is that the HTTP/2 stream got an HTTP/2 response (due to load balancer config erroring out on the bad content-type) rather than the full gRPC status-based mechanism, I imagine. This ended up confusing its handlers in not getting the payloads it expected. I can generate traces of the h2_stream but the http2 client seems to be working fine and I assumed the narrower one on grpcbox + otel would be sufficient. |
Yea, this is all I need. I'm simply having |
Currently the client will end up timing out when at least some error status codes are returned by the server instead of returning those errors.
@ferd do you have the erlang traces still that show this happening?
The text was updated successfully, but these errors were encountered: