I think I have encountered an issue related to this update. I have a Jupyter Notebook that used to launch directly into appmode when accessed using the following link:
404 : Not Found You are requesting a page that does not exist!
A workaround detailed here apparently solved this issue, but is now also broken, potentially by this update.
Below is a log produced by running
less ~/.jupyter-server-log.txt
in the terminal accessed from the notebook by altering the above url after appmode launch failure.
Any suggestions for how to get around this issue would be greatly appreciated.
** log **
Launching jupyter-lab
[I 2023-03-16 22:47:37.798 ServerApp] jupyter_offlinenotebook | extension was successfully linked.
[I 2023-03-16 22:47:37.799 ServerApp] jupyter_resource_usage | extension was successfully linked.
[W 2023-03-16 22:47:37.801 LabApp] ‘base_url’ has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2023-03-16 22:47:37.801 LabApp] ‘token’ has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2023-03-16 22:47:37.801 LabApp] ‘trust_xheaders’ has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2023-03-16 22:47:37.801 LabApp] ‘allow_origin’ has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[W 2023-03-16 22:47:37.801 LabApp] ‘allow_origin_pat’ has moved from NotebookApp to ServerApp. This config will be passed to ServerApp. Be sure to update your config before our next release.
[I 2023-03-16 22:47:37.806 ServerApp] jupyterlab | extension was successfully linked.
[W 2023-03-16 22:47:37.809 NotebookApp] ‘extra_template_paths’ was found in both/home/jovyan/.jupyter-server-log.txt
I just discovered mybinder recently, but I experience issues with installing dependencies using a requirements.yml file. It’s in the root directory of the repository, but it seems to be completely ignored when building the docker image. I’ve tested the file with a conda env create -f requirements.yml locally, and it works well. Can this be an issue related to the update?