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

fix(ext/node): fix grpc error_handling example #23755

Merged
merged 6 commits into from
May 16, 2024

Conversation

satyarohith
Copy link
Member

@satyarohith satyarohith commented May 9, 2024

When we're emitting the 'response' event, we currently have the flags argument set to 0 instead of extracting it from the headers frame. We currently don't have a low level API to extract the flags field from HEADERS frame.

gRPC depends only on the END_STREAM flag to emit "trailers" event which is reponsible to propagate the errors correctly. This PR uses Body::is_end_stream() to determine if a stream will end and set the END_STREAM flag.

TODO:

  • test (added a smoke test in internal repo)

Towards #23714

satyarohith and others added 2 commits May 14, 2024 09:31
Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
@satyarohith satyarohith marked this pull request as ready for review May 14, 2024 14:16
@satyarohith satyarohith merged commit 7893ab9 into denoland:main May 16, 2024
17 checks passed
@satyarohith satyarohith deleted the grpc_error_handling branch May 16, 2024 12:12
bartlomieju added a commit that referenced this pull request May 16, 2024
gRPC depends only on the END_STREAM flag to emit "trailers" event which
is responsible to propagate the errors correctly. This patch uses
Body::is_end_stream() to determine if a stream will end and set the
END_STREAM flag.

Co-authored-by: Bartek Iwańczuk <biwanczuk@gmail.com>
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.

None yet

2 participants