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
When a websocket route that contains some spawned tasks all finish, I expect the worker associated to shut down.
Current Behavior
My websocket route finishes, the spawned tasks finish but only when I shutdown the application do I see a "force shutdown worker, closing x connections" for all the connections that have finished way earlier
Possible Solution
Some pointers on how to diagnose this further
Steps to Reproduce (for bugs)
Use the default websocket example
Spawn some tasks inside the route
Close client
Close server -> see how many connections are closed
Expected Behavior
When a websocket route that contains some spawned tasks all finish, I expect the worker associated to shut down.
Current Behavior
My websocket route finishes, the spawned tasks finish but only when I shutdown the application do I see a "force shutdown worker, closing x connections" for all the connections that have finished way earlier
Possible Solution
Some pointers on how to diagnose this further
Steps to Reproduce (for bugs)
Context
Your Environment
rustc -V
): 1.8.2actix-*
crate versions: actix-ws 0.3.0, actix-web 4.9.0, actix-cors 0.7.0The text was updated successfully, but these errors were encountered: