jupyter-remote-desktop-proxy
jupyter-remote-desktop-proxy copied to clipboard
Add an integration test for VNC + websockify
This tests the following components:
- The VNC server
- websockify
- Jupyter Server Proxy
- The desktop environment itself
It does so by:
- Building the container image
- Starting a container with that image, with jupyter server running inside.
- Connecting to the container via websockets, authenticating and exposing the websocket connection as a regular TCP socket on localhost via websocat
- Taking a screenshot of the remote desktop by connecting to it
through
vncdotool. This requires a tcp connection, hence the double proxying with websocat - Verify that the image produced by the screenshot is the same as a reference image we have.
This only misses the noVNC + JS from testing, but otherwise represents a massive improvement to the status quo!
:point_left: Launch a binder notebook on this branch for commit 7436a5bad080b13d999a48d549b51a72cd381e3c
I will automatically update this comment whenever this PR is modified
:point_left: Launch a binder notebook on this branch for commit 942b910c5fddbe65e1a7928349ca309366478c34
:point_left: Launch a binder notebook on this branch for commit a33a447c714955e9b1176192bae3a89d8fd63cb1
:point_left: Launch a binder notebook on this branch for commit 3a2b964e92e90ecccacd04506778d26213c55d38
:point_left: Launch a binder notebook on this branch for commit 8ea28eb109f902796e7b44b6cd13ee59b15f0e70
:point_left: Launch a binder notebook on this branch for commit c285c0ba823d451fa24997acc1acf0ec974f8c87
:point_left: Launch a binder notebook on this branch for commit 7a59e95d20fd576abf4f0a4e1e50915509b30787
This works perfectly fine locally, but unfortunately something is causing it to hang when the VNC client is trying to connect to the server on GitHub actions. will have to debug next time i get a chance.
Not needed, now that we have #119