You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating server-side stream from Flutter client to Rust server (using tonic). When I'm gracefully stopping the server, it cancels all in-progress streams. However, grpc-dart client doesn't stop the streaming call when canceled from the server, thus making the server hang during shutdown.
This is not server implementation's fault. I verified that the stream gets cancelled by making the streaming call from Postman.
grpc-dart version: 3.2.3
Repro steps
Create a server with server-side streaming RPC.
Connect to the server and invoke this RPC.
Stop the server (or cancel the stream from the server).
Observe that grpc-dart client doesn't notice the cancellation and the server hangs.
Expected result: When the call is cancelled on the server, stream should close on the client side.
Actual result: Stream doesn't close when the call is cancelled from the server.
The text was updated successfully, but these errors were encountered:
This is a low-level HTTP2 event, which is not exposed in the package. The recommendation in the comment above is to wait for some amount before force-shutting down. shutdownNow is not implemented here, but I would be happy to review a PR for this feature.
I am creating server-side stream from Flutter client to Rust server (using tonic). When I'm gracefully stopping the server, it cancels all in-progress streams. However, grpc-dart client doesn't stop the streaming call when canceled from the server, thus making the server hang during shutdown.
This is not server implementation's fault. I verified that the stream gets cancelled by making the streaming call from Postman.
grpc-dart version: 3.2.3
Repro steps
Expected result: When the call is cancelled on the server, stream should close on the client side.
Actual result: Stream doesn't close when the call is cancelled from the server.
The text was updated successfully, but these errors were encountered: