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

Dask Dashboard "More" tab not accessible from "Workers" tab #5136

Closed
avriiil opened this issue Jul 29, 2021 · 7 comments · Fixed by #5175
Closed

Dask Dashboard "More" tab not accessible from "Workers" tab #5136

avriiil opened this issue Jul 29, 2021 · 7 comments · Fixed by #5175

Comments

@avriiil
Copy link
Contributor

avriiil commented Jul 29, 2021

What happened:
When on the "Workers" page of the Dask Dashboard, the "More" tab is not fully accessible.
It drops down but I can't navigate to any items past "Groups". Seems like there's a conflict with the underlaying information in the read/write columns of the workers. See screencast below.

Screen.Recording.2021-07-29.at.08.36.54.mov

What you expected to happen:
To be able to click on items in the "More" tab like "CPU", "Cluster Memory", etc. etc.

Minimal Complete Verifiable Example:

import coiled
import dask.dataframe as  dd
from dask.distributed import LocalCluster

client = LocalCluster()
client

Anything else we need to know?:

Environment:

  • Dask/Distributed version: 2021.07.1
  • Bokeh version: 2.3.3
  • Python version: 3.8
  • Operating System: OS 11.3.1
  • Install method (conda, pip, source): conda

[EDIT]

  • Browser: Brave 1.27.108, Chrome 92.0.45 , Firefox 90.0.2
  • clearing the cache does not resolve the issue for me
@fjetter
Copy link
Member

fjetter commented Jul 29, 2021

I'm neither a bokeh nor a JS specialist so I won't be able to resolve this. However, this kind of thing sometimes relates to browser versions. You could try a different browser and/or see if there is an update for yours available. Either way it will likely be useful if you can post which browser+version you are using.
Lastly, with the newly introduced tabs, we've seen issues related to browser caching. Does clearing your browser cache help?

@avriiil
Copy link
Contributor Author

avriiil commented Jul 29, 2021

Thanks @fjetter, forgot to list my browsers indeed!
I've updated my issue above, listing browsers and respective versions.
Clearing the cache didn't help for me, unfortunately.

@jrbourbeau
Copy link
Member

cc @jacobtomlinson

@jacobtomlinson
Copy link
Member

Interesting! It looks like the z-index of the content in the workers table is being set higher than the dropdown and is therefore sitting in front. This breaks the hover functionality.

However I am unable to reproduce in Firefox, Chrome or Safari on macOS.

@ncclementi
Copy link
Member

I can reproduce on Firefox 90.0.2 and Safari 14.1.1 on macOS, and clearing the cache does not resolve the issue for me either.
Currently on Dask and Distributed 2021.07.2 (and I've tried with distributed main too) and I see the same as @rrpelgrim

more_tab_workers

cc @jsignell

@jsignell
Copy link
Member

jsignell commented Aug 5, 2021

Yeah I can reproduce on any browser. As @jacobtomlinson suggested, I set the z-index for the workers table to 0 in my dev console and that seems to fix it. Now it's just a matter of finding where to put that in the codebase :)

@jacobtomlinson
Copy link
Member

No idea why I wasn't able to reproduce this but things should be good now! Thanks @jsignell.

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

Successfully merging a pull request may close this issue.

6 participants