Skip to content
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

Enter Dashboard URL text field: pressing Enter is different from pressing the search button #202

Open
consideRatio opened this issue Jul 28, 2021 · 2 comments

Comments

@consideRatio
Copy link

consideRatio commented Jul 28, 2021

What happened:

Pressing Enter compared to pressing the Search icon when having entered a Dask Dashboard URL provides different outcomes.

image

dask-labextension-search-vs-enter

I've realized that if I hover the Search icon button, it sais "Auto-detect Dashboard URL" which is what has confused me, pressing enter and doing a "auto-detect dashboard URLs" are different, but based on the layout I assumed they were the same: to submit the suggested URL explicitly written out.

My wish

I wish that the UI didn't end up confusing me. I have never been able to have a functional auto-detect button, and that probably makes me even more confused.

Minimal Complete Verifiable Example:

I don't know how to provide this =/

Environment:

JupyterHub (1.1.1 Helm chart) + Dask-Gateway (0.9.0 Helm chart).

$ conda list | grep dask
dask                      2021.6.0           pyhd8ed1ab_0    conda-forge
dask-core                 2021.6.0           pyhd8ed1ab_0    conda-forge
dask-gateway              0.9.0            py38h578d9bd_0    conda-forge
dask-glm                  0.2.0                      py_1    conda-forge
dask-kubernetes           2021.3.1           pyhd8ed1ab_0    conda-forge
dask-labextension         5.0.2              pyhd8ed1ab_0    conda-forge
dask-ml                   1.9.0              pyhd8ed1ab_0    conda-forge
pangeo-dask               2021.06.05           hd8ed1ab_0    conda-forge
$ python --version
Python 3.8.10

Operating System: Ubuntu 20.04
Install method: conda-forge

DASK_DISTRIBUTED__DASHBOARD_LINK=/user/{JUPYTERHUB_USER}/proxy/{port}/status
DASK_GATEWAY__ADDRESS=http://10.100.116.39:8000/services/dask-gateway/
DASK_GATEWAY__AUTH__TYPE=jupyterhub
DASK_GATEWAY__CLUSTER__OPTIONS__IMAGE={JUPYTER_IMAGE_SPEC}
DASK_GATEWAY__PROXY_ADDRESS=gateway://traefik-prod-dask-gateway.prod:80
DASK_GATEWAY__PUBLIC_ADDRESS=/services/dask-gateway/
DASK_LABEXTENSION__FACTORY__CLASS=GatewayCluster
DASK_LABEXTENSION__FACTORY__MODULE=dask_gateway
DASK_ROOT_CONFIG=/srv/conda/etc
@ian-r-rose
Copy link
Collaborator

I've realized that if I hover the Search icon button, it sais "Auto-detect Dashboard URL" which is what has confused me, pressing enter and doing a "auto-detect dashboard URLs" are different, but based on the layout I assumed they were the same: to submit the suggested URL explicitly written out.

Enter checks the url that you have entered in the box, while the "auto-detect" button tries to find the appropriate URL in your currently active notebook. I suspect what is confusing you is that "Auto-detect" isn't working for your dask-gateway setup, though it's tough for me to tell for sure.

My wish

I wish that the UI didn't end up confusing me. I have never been able to have a functional auto-detect button, and that probably makes me even more confused.

I suggest trying a LocalCluster to get a feel for the intended use of the detect button. Getting dask-gateway working with the labextension is tricky, and nobody has really been resourced to work on it, so I'm not sure what the latest is there (see some discussion in #135 and #190).

@agoose77
Copy link

agoose77 commented Aug 31, 2021

I Haven't got much to add here besides remarking that this has confused me too in the past for similar reasons as @consideRatio.

I would expect either

  • two buttons, one that populates the URL field, another that tries to connect to the cluster
  • one button, but with different behaviour according to whether the URL field is empty

IIRC my issues were particularly pronounced when I was using a remote cluster linked via an SSH tunnel,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants