Skip to content
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

Propagate gRPC status code when not ok #519

Merged
merged 11 commits into from
Oct 24, 2023

Conversation

jfallows
Copy link
Contributor

Description

When gRPC response status code arrives in HTTP response headers (not trailers), typically due to being an error of some kind (not OK status), then make sure it is conveyed consistently back to the gRPC client.

Fixes #504

@jfallows jfallows marked this pull request as ready for review October 23, 2023 20:28
write notify SENT_ASYNC_REQUEST
read closed

connect await SENT_ASYNC_REQUEST
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why it is called ASYNC as far as I know there is no such terminology in grpc as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Async over a pair of Kafka topics.

@jfallows jfallows merged commit f1985a3 into aklivity:develop Oct 24, 2023
5 checks passed
@jfallows jfallows deleted the bug/grpc-status-code-not-ok branch October 24, 2023 00:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

gRPC method call doesn't respond when status code is not OK
2 participants