-
-
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
CORS Errors #23
Comments
It was suggested in the linked issue to use My JupyterLab instance is spawned in a container via JupyterHub on a HPC grid. In JupyterLab I can spawn a dask cluster on the same HPC grid and I would like to use this extension to monitor the progress of the dask cluster from within the JupyterLab app. The scheduler isn't running within the JupyterLab container itself so isn't available from localhost which IIUC is all I can open a separate tab and monitor the dask cluster that way but it would be very cool to be able to do so from within JupyterLab itself, in particular to be able to arrange several windows and monitor different metrics at the same time... as shown in #18 (comment) |
As an interim workaround how would I disable CORS as mentioned in #22 (comment)? |
I'm not sure it's relevant, but considering the below: dask-labextension/src/widget.tsx Lines 433 to 438 in 1d2e87a
In a new tab I can access If I can't even access that url outside of JupyterLab, maybe that codepath won't work for me and causes the below error even though it is a dask dashboard:
|
Ok, it appears that ...so I'm likely just using too old of a version! It does appear to be in the latest release so I jsut need to update... |
Beat me to it! Yeah, the location to the image recently changed. We clearly need to get some proxy recommendations in place, but for the moment: CORS policies tend to be buried in browser settings. They will, in general, be different from browser-to-browser. In particular, it seems the CORB (note B) problem you are seeing might be specific to Chrome. |
Wondering if jupyter/notebook#3886 will help at all |
As discussed in #21 (comment) I'm seeing CORS errors when using this extension:
I'm opening a separate issue here to discuss possible workarounds/fixes
The text was updated successfully, but these errors were encountered: