-
Notifications
You must be signed in to change notification settings - Fork 7
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
Closing a stream can throw if messages aren't waited for #43
Comments
glbrntt
added a commit
to glbrntt/grpc-swift-nio-transport
that referenced
this issue
Dec 6, 2024
Motivation: A couple of tests fail sometimes, the root cause of which is grpc#43. Modifications: - Wait for all messages to be received before closing Result: Tests are more stable
Merged
glbrntt
added a commit
that referenced
this issue
Dec 6, 2024
Motivation: A couple of tests fail sometimes, the root cause of which is #43. Modifications: - Wait for all messages to be received before closing Result: Tests are more stable
gjcairo
added a commit
that referenced
this issue
Jan 17, 2025
This has been resolved in apple/swift-nio#3032 and the fix is present in NIO since 2.78.0, which this package already depends on. The workaround is removed in #63. Closing. |
glbrntt
pushed a commit
that referenced
this issue
Jan 17, 2025
This has been resolved in apple/swift-nio#3032 and the fix is present in NIO since 2.78.0, which this package already depends on. Removing workaround in tests.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If a client response handler returns before all messages have been received (i.e. the user has what they need from the response) then the stream might throw because of an unclean close.
This can happens because the HTTP/2 stream closes uncleanly and NIO's async channel throws this error.
The text was updated successfully, but these errors were encountered: