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
For some reason, the await server.wait_closed() in start_server never completes, but it does in shutdown_server.
I was able to "fix" this locally by just doing the await server.wait_closed() in a loop with a timeout. Not sure what a minimal reproduction would be. For me, it seems to happen after I've done any gRPC request (it works fine if the shutdown happens before any requests are received, but if the server has handled even unary/unary requests, it doesn't...).
The text was updated successfully, but these errors were encountered:
Currently grpclib cancels all current requests and waits until they finish. But when new requests come this don't works as expected.
What should be done: grpclib should send GOAWAY frame and complete all current requests. GOAWAY makes it possible to stop new requests coming. But currently sending GOAWAY frame is almost equal to immediately closing an entire connection.
I'm not entirely sure what this issue is.
Basically, I have a server.
elsewhere, I have a function that's triggered when the app has requested a shutdown.
For some reason, the
await server.wait_closed()
instart_server
never completes, but it does inshutdown_server
.I was able to "fix" this locally by just doing the
await server.wait_closed()
in a loop with a timeout. Not sure what a minimal reproduction would be. For me, it seems to happen after I've done any gRPC request (it works fine if the shutdown happens before any requests are received, but if the server has handled even unary/unary requests, it doesn't...).The text was updated successfully, but these errors were encountered: