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
I'm going to try pinning jupyter_server<15 to see if that fixes it (jupyter-server/jupyter_server#727). I unfortunately don't have access to the jupyterhub logs to actually see any reported errors...
I sent a request to 2i2c to see if we can test new images at https://staging.uwhackweeks.2i2c.cloud. Note this is a tricky thing because executing our notebooks works fine, as does running the docker image locally (docker run -it --name HACKWEEK -p 8888:8888 uwhackweek/icesat2:2022.03.15 jupyter lab --ip 0.0.0.0 ), the 404 error only surfaces when running the image via jupyterhub. cc @jomey@sgibson91
For now I've reverted to uwhackweek/icesat2:2022.03.11
The text was updated successfully, but these errors were encountered:
Trying to access https://uwhackweeks.2i2c.cloud/user/scottyhq/lab results in a 404 error.
From image 2022.03.11 -> 2022.03.15 we changed:
I'm going to try pinning
jupyter_server<15
to see if that fixes it (jupyter-server/jupyter_server#727). I unfortunately don't have access to the jupyterhub logs to actually see any reported errors...I sent a request to 2i2c to see if we can test new images at https://staging.uwhackweeks.2i2c.cloud. Note this is a tricky thing because executing our notebooks works fine, as does running the docker image locally (
docker run -it --name HACKWEEK -p 8888:8888 uwhackweek/icesat2:2022.03.15 jupyter lab --ip 0.0.0.0
), the 404 error only surfaces when running the image via jupyterhub. cc @jomey @sgibson91For now I've reverted to
uwhackweek/icesat2:2022.03.11
The text was updated successfully, but these errors were encountered: