Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Docs about CORS: Accessing a cloud-local dask cluster as a JupyterHub user
See original GitHub issueI hoped that the #34 #31 should accomplish something allowing me to use this extension in a way that allowed me to write a scheduler URL that is only accessible from the jupyter server but not from the browser client.
For example, in a terminal in the jupyter server made available through a JupyterHub, I can wget to http://dask-scheduler.dask:8787, but from the browser, I cant access that URL. It is only available in the local network of the Jupyter server.
Question
Was this supposed to work after #31 #34, or were those PRs not meant to accomplish this as I hoped they were with a lack for a proper understanding.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:13 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m putting together a tutorial right now - adapted from dask/dask-tutorial and focused more on the kind of use-case discussed here (for my purposes, running single-machine Dask via Gigantum on Digital Ocean). I will digest the contents of this issue there, but it seems this isn’t quite documented anywhere. Is there a place that it should be documented?
@mangecoeur that is correct.