When a running execution is stopped by the client (through the WebSocket connection), we immediately call close_client_connection to terminate Tubesock connection to the browser and stop the runner. However, since the regular workflow also included a call to close_client_connection, it might have been called twice.
When a running execution is stopped by the client (through the WebSocket connection), we immediately call
close_client_connectionto terminate Tubesock connection to the browser and stop the runner. However, since the regular workflow also included a call toclose_client_connection, it might have been called twice.