-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
500 Error at launch (KeyError: 'terminals_available' in self.settings) #255
Comments
Partial fix:
seems to partially fix it -- there are errors in the terminal, but it runs. This appears to be a config problem in some interaction between how homebrew and jupyter set paths? (As such, I suspect that this is closely related to jupyter/notebook#6974) |
cc @echarles @RRosio @ericsnekbytes for awareness |
See also jupyterlab/jupyterlab#14890 |
jupyter_server_terminals's latest update added the following to respect terminal setting:
So if enable_terminal is set to false then it is guaranteed to fail the nbclassic/tree. Link to jupyter_server_terminals: jupyter-server/jupyter_server_terminals#85 |
Also reported on discourse.
macOS 13.5, Python 3.11.4 (homebrew)
With the recent move to notebook 7, I have been having issues with both
notebook
(documented here and here) andnbclassic
.For the latter, I am seeing a traceback, followed by a 500 error in the browser:
If I change "/opt/homebrew/lib/python3.11/site-packages/nbclassic/tree/handlers.py", line 69 from
to
(as is done in
notebook/app.py
) it works (no errors, no 500), but I assume this shouldn't be necessary (and perhaps hides a real bug or config issue)?I assume it is a local config issue somehow, but in fact even if I get rid of all of the current directories listed with
jupyter --paths
it does not seem to help.(There seem to be other interface problems as documented in my
jupyter/notebook
issue. Also, if relevant: Python 3.11 is installed by homebrew, but all packages, including jupyter, notebook, etc. are installed with pip.)Any ideas?
The text was updated successfully, but these errors were encountered: