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 the problem described at canonical/operator#1246, this issue represents the Pebble side: we should fix the /v1/tasks/{task_id}/websocket/{websocket_id} endpoint so that if the Pebble side has already timed out ("timeout waiting for websocket connections"), we should time out (or cancel immediately) attempts to connect to that websocket URL.
For the problem described at canonical/operator#1246, this issue represents the Pebble side: we should fix the
/v1/tasks/{task_id}/websocket/{websocket_id}
endpoint so that if the Pebble side has already timed out ("timeout waiting for websocket connections"), we should time out (or cancel immediately) attempts to connect to that websocket URL.Marking as Low Priority given the Ops-side fix at canonical/operator#1247.
The text was updated successfully, but these errors were encountered: