Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure websocket endpoint times out if it's never going to happen #422

Open
benhoyt opened this issue Jun 5, 2024 · 0 comments
Open

Ensure websocket endpoint times out if it's never going to happen #422

benhoyt opened this issue Jun 5, 2024 · 0 comments
Labels
Bug An undesired feature ;-) Low Priority The opposite of "Priority"

Comments

@benhoyt
Copy link
Contributor

benhoyt commented Jun 5, 2024

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.

@benhoyt benhoyt added Bug An undesired feature ;-) Low Priority The opposite of "Priority" labels Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug An undesired feature ;-) Low Priority The opposite of "Priority"
Projects
None yet
Development

No branches or pull requests

1 participant