You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What happened:
labextension dashboard launcher url saved in jupyterlab workspace, causing repeating 503, 403 & 404 network errors every second after a cluster is shut down or the next time users open up a jupyterhub session:
Errors such as this appear in the console every few seconds:
dask-logo.svg:1 GET https://staging.aws-uswest2.pangeo.io/services/dask-gateway/clusters/icesat2-staging.24e564509dbd475abd71272306fbba06/statics/images/dask-logo.svg?1602869144274 503
Image (async)
vendors~main.0696ed76febe5543ce98.js:2 GET https://aws-uswest2.pangeo.io/user/scottyhq/dask/dashboard/5b22bb4e-80fa-4803-84cd-5dc7fdd97f06/individual-plots.json?1602875598184 404 (or 403)
As far as I can tell these errors are coming from the dashboard URL persisting in /home/jovyan/.jupyter/lab/workspaces/*:
key entry seeming to be this if the status url is manually copied into the sidebar "dask-dashboard-launcher":{"url":"https://staging.aws-uswest2.pangeo.io/services/dask-gateway/clusters/icesat2-staging.24e564509dbd475abd71272306fbba06/status","cluster":""} Or, if a Gateway cluster is created from the lab-extension this config remains: "dask-dashboard-launcher":{"url":"dask/dashboard/5b22bb4e-80fa-4803-84cd-5dc7fdd97f06","cluster":""}
What you expected to happen:
I expect the URL to disappear from workspace config when a kernel is restarted, when I manually delete the URL from the dask-labextension dashboard, or when I logout.
Current workaround:
Go to the https://aws-uswest2.pangeo.io/user/scottyhq/lab?reset in order to remove the last URL from the workspace. Would be nice to have the URL reset whenever a kernel is restarted, user logs out, or cluster is shut down.
My understanding is that the dashboard url needs to be saved to the workspace so that if you refresh the browser tab, the same panes are open and the same client is connected. So like you say, we'd need to explicitly unsave the url from the state.
We could try to do this in the cases that you list, or we could give up on a client after it fails a certain number of times. Do you think that would be a reasonable solution?
What happened:
labextension dashboard launcher url saved in jupyterlab workspace, causing repeating 503, 403 & 404 network errors every second after a cluster is shut down or the next time users open up a jupyterhub session:
Errors such as this appear in the console every few seconds:
As far as I can tell these errors are coming from the dashboard URL persisting in
/home/jovyan/.jupyter/lab/workspaces/*
:key entry seeming to be this if the status url is manually copied into the sidebar
"dask-dashboard-launcher":{"url":"https://staging.aws-uswest2.pangeo.io/services/dask-gateway/clusters/icesat2-staging.24e564509dbd475abd71272306fbba06/status","cluster":""}
Or, if a Gateway cluster is created from the lab-extension this config remains:"dask-dashboard-launcher":{"url":"dask/dashboard/5b22bb4e-80fa-4803-84cd-5dc7fdd97f06","cluster":""}
What you expected to happen:
I expect the URL to disappear from workspace config when a kernel is restarted, when I manually delete the URL from the dask-labextension dashboard, or when I logout.
Environment: ( jupyterhub on kubernetes)
Current workaround:
Go to the
https://aws-uswest2.pangeo.io/user/scottyhq/lab?reset
in order to remove the last URL from the workspace. Would be nice to have the URL reset whenever a kernel is restarted, user logs out, or cluster is shut down.Related issues
cc @ian-r-rose , @TomAugspurger , @jcrist
#20, #135, pangeo-data/pangeo-cloud-federation#786
The text was updated successfully, but these errors were encountered: