I have an installer that builds a venv, installs notebook, and runs a notebook. It’s been working for weeks, and has brought the notebook up in the default browser.
Nothing is pinned yet, so I get whatever the ‘newest’ stuff is, when I rebuild the venv (which is always), because I’m testing the installer. Just this weekend, it stopped working. Notebook server starts up fine, serves a page, and it’s empty. Whereas I used to see a bunch of stuff in the JS console, now I just have an error.
Here’s what I’m seeing. Where it seems to be dying is in this call o(958).
Thank you for reporting this. I would encourage you to open an issue on Issues · jupyter/notebook · GitHub with more details (browser and version, operatying system, exact version of notebook package) - this will help to understand the issue better.
Now that (this leg of) the Death March is over, I have some time to try and make a minimally reproducible example.
> bash -i
bash-3.2$ more JupyterBug.bash
python3.10 -m venv notebook_venv
pip install --upgrade pip setuptools
pip install --force-reinstall "notebook==7.0.3"
/usr/libexec/PlistBuddy -c 'Print :CFBundleShortVersionString' /Applications/Safari.app/Contents/Info.plist
open -a /Applications/Safari.app/Contents/MacOS/Safari 2> /dev/null &
jupyter-notebook & # notebook comes up with blank page
jupyter notebook stop
I was able to reproduce the failure with this. Clearing the browser cache ended up letting it work, and I got a notebook page.
I was AFK much of last Friday and Saturday and I ran into this issue on Sunday, I believe. 7.0.3 dropped on… Thursday?
Perhaps something in browser cache that 7.0.2 was fine with but 7.0.3 wasn’t?
I can post my output for the script if this doesn’t explain, but I don’t know that it’s going to tell anyone anything about what was in cache…