-
-
Notifications
You must be signed in to change notification settings - Fork 63
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
404 GET /dask/dashboard/... in console #164
Comments
Thanks for the update Jacob. I've tried clearing the URL but this doesn't prevent the messages from appearing, even after restarting jupyter lab. Is this something that appears with MacOS environments? My Windows 10 environment doesn't seem to have this behaviour when I start then shutdown local dask clusters. |
It shouldn't make a difference. Are you running the same version of the lab extension? |
In MacOS, I am running dask-labextension=2.0.1 and in Win10 dask-labextension=2.0.0 Is there anything else you can suggest I could try? Environments Mac OS |
Could you update to a more recent version? Latest is |
I've tried updating to
I'll do some further investigation and see if I can replicate this behaviour on another Win10 virtual environment to see if it is potentially an OS related issue. |
I have the same problem (dask-labextension 4.0.1 running in an ubuntu-based container on a centos server, connected via opera on macos). Clearing the dask dashboard url, as suggested above, doesn't stop it but it does change the message to: [W 18:39:00.084 LabApp] 404 GET /individual-plots.json?1610303940078 (192.168.1.44) 2.300000ms referer=http://192.168.1.5:8888/lab? |
++ to the issue on LocalCluster. I would idolize the MVP who can point out what I did wrong. Thank you in advance. Environment used pip for all the installs Installed for the first time on Linux Mint: 404 errors from these URLs: (unlike @dipbasu, error comes from ServerApp, not LabApp)
When clicking "New" in the Dask panel, nothing happens same when entering LocalCluster URL. Dashboard is visible at the IP address returned after initializing cluster by from dask.distributed import Client
client = Client()
client All the extensions appear to be enabled and work $ jupyter serverextension list
config dir: /home/maxim/.jupyter
dask_labextension enabled
- Validating...
dask_labextension 5.0.0 OK
jupyter_server_proxy enabled
- Validating...
jupyter_server_proxy OK
jupyterlab enabled
- Validating...$ jupyter labextension list
JupyterLab v3.0.5
/home/maxim/.local/share/jupyter/labextensions
dask-labextension v5.0.0 enabled OK (python, dask_labextension)
@jupyter-widgets/jupyterlab-manager v3.0.0 enabled OK (python, jupyterlab_widgets)
Other labextensions (built into JupyterLab)
app dir: /home/maxim/.local/share/jupyter/lab
jupyterlab 3.0.5 OK
$ jupyter labextension list
JupyterLab v3.0.5
/home/maxim/.local/share/jupyter/labextensions
dask-labextension v5.0.0 enabled OK (python, dask_labextension)
@jupyter-widgets/jupyterlab-manager v3.0.0 enabled OK (python, jupyterlab_widgets)
Other labextensions (built into JupyterLab)
app dir: /home/maxim/.local/share/jupyter/lab I open JupyterLab with |
When shutting down a LocalCluster I receive 404 GET /dask/dashboard/.../individual-plots.json? messages in the console window E.g.
If I restart jupyter lab, these messages continue appear even when I am not working with dask.
They stop if I start a new cluster but they reappear if the cluster is shutdown again.
It's not a big issue but more of an annoyance as I may miss important messages in the console as the warning repeats every two seconds.
I suspect it is related to how the dask-dashboard-launcher entry in the lab-xxx.jupyterlab-workspace file (located in .jupyter/lab/workspaces) is used. E.g.
Environment:
Let me know if you require further information
The text was updated successfully, but these errors were encountered: