Missing or misshapen translation settings schema #6974
Comments
|
Thanks @taktikal17 for reporting the issue 👍
Just to confirm: does JupyterLab work without specifying the |
|
I am seeing something similar, also possibly with some weird interactions with jupyterlab. (I think on one of my machines it is failing at a different Also possibly related:
|
|
same issue here, notebook version 6.5.4 had no issue. ❯ jupyter --version |
|
cc @andrii-i @RRosio @ericsnekbytes @echarles @afshin If one of you has a Mac and would be able to look into this that would be great, thanks 🙏 |
|
A further possibly useful bit of info: On my setup, Python 3.11 is installed by homebrew, but all packages, including jupyter, notebook, etc. are installed with pip. |
|
I note that is a partial fix: it still gives error messages in the terminal, but the interface issues mentioned above seem to be better. So it is possible that this is an issue of "miscommunication" between the homebrew build and jupyter? |
|
Further to my previous partial fix using I note that in fact In detail: without the variables set, the "Installed" list is empty and, for example, there is no sidebar entry for ipyparallel even when installed: 
When run with those variables set, I get: 
|
|
Things seem a little different with the just-released Notebook 7.0.1. Now, On the other hand |
Could this be similar to #6952, which would happen when updating I tried creating a new environment, installing Would you be able to try install |
|
My experience replicating this issue was as follows: I installed Python 3.11 with homebrew and then the Notebook package with With Notebook 7.0.1
Indeed, Jupyterlab works well using I have only encountered this issue with when using the python/pip installed with homebrew. All my installs of Notebook 7 with conda environments work well. This is not my regular workflow, I usually use conda environments, so I am not sure yet what could be the problem. |
|
(@RRosio, I'm glad you see the same (or very similar) issue!...) @jtpio, Sorry if I wasn't clear -- this isn't in a venv, but in the "base" python environment (i.e., my homebrew install, but not in a venv; not the system python). In fact, it look likes the blank page issue is indeed a local authentication or cache issue, which happens irrespective of whether I'm in a venv or the base environment. Clearing the browser cache seems to solve the problem. So apologies for that red herring. But the other problems described in this thread remain:
Sorry for the confusion related to 7.0.1 -- but this list now seems like a summary of all the actual issues I am experiencing.... (nb. I am not sure when/if I ran |
|
(I wonder if this — basically, the above list — should become a new/separate issue to highlight that it’s not only about the “schema” problem?) |
|
Thanks @defjaf for posting these details it will help reproduce the issue more easily 👍
If this is also an issue with JupyterLab, would you be able to open an issue on the JupyterLab repo? https://github.com/jupyterlab/jupyterlab Thanks! |
|
See also jupyterlab/jupyterlab#14890 |
|
Adding a data point, I had the same issue occur on macOS today, installing via pip Following command-line error logs, I was able to run build with |
I am experiencing the same problems when running |
|
-- Workaround --
*Note - I don't think you need to uninstall Homebrew's python or notebook libraries since Anaconda runs its own instance of python and notebook libraries in a separate directory from Homebrew's. |
|
@stgreenman (et al): I don't use (Ana)conda, but this should work. However, if you just want to stick with homebrew, you should just be able to add the following to your .bashrc (or equivalent for other shells): export JUPYTER_PATH=/opt/homebrew/share/jupyter
export JUPYTER_CONFIG_PATH=/opt/homebrew/etc/jupyterAlternately, you can also just create (and activate) a venv with homebrew python, and that should work as well (with no extra configuration). (For clarity: setting the environment variables seems to fix the UI issues in notebook, but the schema console messages still appear on my configuration. Using a venv seems to fix the UI issues and the schema messages.) |
|
So, now that this (and the related jupyterlab and nbclassic issues) have been sitting here for a while, do we have a picture of whether this is deemed a proper, fixable (and fix-worthy) bug? If so, do we understand whether it's likely on the jupyter-* side, or is it possibly actually a homebrew issue? (I haven't reported it over there, and I don't think anyone else has either — although see this list of supposedly closed issues — but perhaps I or someone should?) (I completely understand that we are discussing voluntary open-source contributions here, so timelines can be long, and that a perfectly acceptable response is: if this bothers you, fix it yourself! Although some pointers for where to look in the code-base would be great...) |
|
I'm having the same issue, can't seem to fix it with the workaround. |
|
I'm seeing the same problem after installing. Python is installed with homebrew and jupyter with pip. On MacOS 12.3.1. I'm seeing: and
does not seem to exist. |
|
TL;DR: Quick fix by making a symlink from where Jupyter is looking to where the files actually are: (Keep in mind your python version might differ so check the Jupyter error output for your version)
I have a fresh apple silicon machine with the latest OS updates. First brew installed python3. Then
As was said earlier the meat of this problem is for whatever reason jupyter notebook is looking for the files So I symlinked: and now things are happy (until I upgrade python at least). Full "stacktrace" below: |
setting env variables did not work, however creating a venv and re-pip installing jupyter notebook inside the venv worked. |
|
FWIW, and as expected, all of these errors and misbehaviours vanish for the python.org framework build (of 3.12, but I assume more generally), without requiring any special environment variables or other changes. This still lets me install packages by pip and not be wedded to using a venv, so I think I am moving back to this infrastructure from homebrew, at least for now. |
|
I had similar issue . Check possible conflicts with |
Hi @defjaf, After installing python.org framework build can one still run other non-pythonic homebrew codes / packages? |
Yep, they can more or less peacefully coexist. (Sometimes a homebrew package will try to install python but it usually doesn't clash, although this can depend on path details.) |
|
So far the easiest fix is from @njo creating a symlink to the missing folder shown in the error message. If you look at one of the errors, for example:
It is complaining that the specified file is not found in target location. When I checked, that's right, there is no jupyter folder inside ...share/ folder. So I created a symlink named jupyter from /opt/homebrew/share/jupyter using the command,
Try running the jupyter notebook command again. This also ensures that you are using homebrew's installed version. |
|
Two cents here: I was having this same problem with both Jupyter notebook and jupyter lab and I solved it with a |
|
I had my Python installed VIA Homebrew (macOS) and i've installed jupyter lab VIA pip3 (pip3 install jupyterlab) but it shows that jupyter lab still comes from homebrew regardless When i ran jupyter lab (by typing "jupyter lab" in terminal) i got these error logs what worked for me was this "build" command that was printed in the error logs (PS: you need Node 18<=, i used NVM) 
I saw these logs while the build command ran, 
i also added these configs to my .zshrc file although i am not sure if it was significant Hope this helps 💯 🍷 🗿 |
|
Make sure that you don't have the notebook package installed in both the global python and the python environment you're working in. In my case I did, so I ran |
|
2 working solutions: The first is to export the following: The second is to simply install an earlier version: |
|
thanks to @avioligo
then run $ jupyter --version, which shows: notebook : 7.0.6
notebook will be replaced to version 6.5.6, and version 7.0.6 is auto deleted.
everything is ok! |
FWIW this ended up fixing the blank |
its worked for me. |
That's awesome, just wanted to add a quick solution for Jupyer Lab as well, just run: |
Works like charm...thanks @njo |
This ended up working for me :) thank you |
|
It seems Jupyter Notebook is not installed anymore with Jupyterlab by default. Run If it says 'not installed', install it manually: Hope that helps. |
it works for me!!! THX! |
|
Simply running the suggested command by @njo fixed this issue for me, thank you! The command was: With the second path being the one given in the |
this works for me perfectly, i have brew python and pip jupyter and thats the point |
|
I encountered this issue due to this -
I am pretty much noob about understanding the whole issue but if you want to quickly run it, try - |
|
we are on windows and have the same issue. as I understand the problem jupyter is searching for the configs in python installation folder but in our case we have jupyter outside of it. the easiest way to test it is by installing jupyter to a custom path: |
and others
I am getting an error when launching jupyter.
I uninstalled everything including python (with brew) and still not solving the issue.
The folder
/opt/homebrew/Cellar/[email protected]/3.11.4_1/Frameworks/Python.framework/Versions/3.11/share/doesn't contain the
jupyterfolder.Here the lib I am ussing:
Jupyter lab would work using
jupyter lab --app-dir /opt/homebrew/share/jupyter/labHow do I change the path to run
jupyter notebook?Thank you
The text was updated successfully, but these errors were encountered: