-
Notifications
You must be signed in to change notification settings - Fork 25
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(destinations): Stop writing resources when channel is closed #460
Merged
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
5174a25
fix(destinations): Stop writing resources when channel is closed
erezrokah 03ab5d9
test: Add test to ensure correct destination error is reported
erezrokah 392854b
Merge branch 'main' into fix/stop_send_eof
erezrokah e0245de
style: Fix linter
erezrokah File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Im not sure i understand what this solved. give in othercase this just returns an error and doesn't write to the channel while with break it actually sends
CloseAndRecv
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Write
works in stream mode (it's not a synchronous RPC), so if we want the correct response/error from the write request we need to callRecvMsg
which is only done inCloseAndRecv
(and only once actually).So
SendMsg
will never return application level error as it doesn't wait for the message to be received by the server.Technically I think we should callRecvMsg
for eachSendMsg
per the docs:> SendMsg does not wait until the message is received by the server. An untimely stream closure may result inlost messages. To ensure delivery, users should ensure the RPC completed successfully using RecvMsg.We don't need ⬆️ as we don't have Bidi-streaming (I think), but still the response is received from
CloseAndRecv
, see https://grpc.io/docs/languages/go/generated-code/#client-streaming-methods-1