jupyter-remote-desktop-proxy
jupyter-remote-desktop-proxy copied to clipboard
Automatically reconnect if we lose connection
This needs much better retry logic, with back-offs and status messages. But fundamentally, it does already work \o/
Fixes https://github.com/jupyterhub/jupyter-remote-desktop-proxy/issues/80
:point_left: Launch a binder notebook on this branch for commit 27f67ce831e01eac905f5336ae9cb2f599a63679
I will automatically update this comment whenever this PR is modified
:point_left: Launch a binder notebook on this branch for commit fab710e8e25271ec545cc435a345b2e0b5000cb2
Excited about this bugfix! I think it would mean that a restart of for example a ingress-nginx or jupyterhub proxy pod would be handled more gracefully.
This needs much better retry logic, with back-offs and status messages.
I'll see if I can get this worked to completion before tuesday. The goal I have made explicit: to provide retry logic with backoff, verify function manually by changing network rules on the fly.
I attempted for an hour or so but failed to make progress =/
Superceeded by https://github.com/jupyterhub/jupyter-remote-desktop-proxy/pull/112