The Dask dashboard is not working on Kaggle. My code is:
from dask.distributed import Client, progress
client = Client()
client
Clicking the Dashboard link says "This site can’t be reached"
I'm guessing that page (e.g. http://127.0.0.1:8787/status) is not being served by Kaggle. Is there any way to get any of the dashboard components to be visible in the notebook? Or would we IFrame something into the notebook?
To reproduce the error please see the Kaggle kernel https://www.kaggle.com/cornhundred/trying-dask-on-kaggle?scriptVersionId=14702415
@quasiben is something like https://github.com/dask/distributed/pull/2715 likely to solve this?
Nope. That's different. This likely needs to be solved on the Kaggle
side. They either need to open up another port, or else use something like
nbserverproxy to allow the Jupyter notebook server to proxy through the
dask dashboard.
I recommend raising a feature request with Kaggle. There isn't much we can
do other than implement tools that can solve this problem. Kaggle needs to
choose to actively use them.
On Sun, May 26, 2019 at 6:28 AM Tom Augspurger notifications@github.com
wrote:
@quasiben https://github.com/quasiben is something like
dask/distributed#2715 https://github.com/dask/distributed/pull/2715
likely to solve this?—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/4844?email_source=notifications&email_token=AACKZTG2LB6ILGAHNUDO2HDPXJX7NA5CNFSM4HPWAAAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWIDY2A#issuecomment-495991912,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACKZTDEXCMITFE3BGKCPOLPXJX7NANCNFSM4HPWAAAA
.
That’s my suspicion too. I’d recommend reaching out to them and pointing them here if they have questions.
Closing for now since there isn’t any immediate step to take here.
Thanks I'll raise the issue with Kaggle
Most helpful comment
Nope. That's different. This likely needs to be solved on the Kaggle
side. They either need to open up another port, or else use something like
nbserverproxy to allow the Jupyter notebook server to proxy through the
dask dashboard.
I recommend raising a feature request with Kaggle. There isn't much we can
do other than implement tools that can solve this problem. Kaggle needs to
choose to actively use them.
On Sun, May 26, 2019 at 6:28 AM Tom Augspurger notifications@github.com
wrote: