-
-
Notifications
You must be signed in to change notification settings - Fork 718
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
Dashboard not loading with Cythonized Scheduler #4760
Comments
Thanks for surfacing this @jakirkham! I tried to reproduce locally but was able to see the dashboard as usual (no errors were logged). I first checked out the latest I've also included the Packages I have installed locally (conda list):
|
My guess is it is not using the Cythonized Scheduler then. Don't know offhand why. Maybe there is still some lingering bits from the pure Python Scheduler? Maybe a fresh environment needs to be used? Ben ran into this when we were doing some other work earlier. Have since reproduced this myself locally as well |
Dug into this a bit locally. The changes in PR ( #4761 ) fix this issue for me. Just to test things a bit further I created an array and computed its sum to make sure something a bit more dynamic worked as well. Switching between tabs seems to work as well |
As a sanity check to ensure the Cythonized Scheduler is used, it might be worth trying the following In [1]: import distributed.scheduler
In [2]: distributed.scheduler
Out[2]: <module 'distributed.scheduler' from '/Users/jkirkham/Developer/distributed/distributed/scheduler.cpython-38-darwin.so'> Note that the filename for the scheduler contains |
Alright, I tried in a fresh env and was able to reproduce the 500 error |
test_scheduler.py contains extensive unit tests for the MemoryState class. Why don't they trip in CI? |
Because CI doesn’t test the Cythonized Scheduler correctly |
This appears to have started recently. Possibly related to PR ( #4651 ) ( cc @crusaderky )? In particular loading the dashboard shows a 500 error. Locally the following exception comes up when the Scheduler is Cythonized. The issue does not occur when pure Python is used.
cc @quasiben
What happened:
What you expected to happen:
Minimal Complete Verifiable Example:
Anything else we need to know?:
Environment:
The text was updated successfully, but these errors were encountered: