Open MircoT opened 2 years ago
No response
If the scheduler job exited with errors (e.g. job status = 4) the dask labextension still stry to connect instead reporting the creation error.
v0.5.9 (Default)
2022-02-22 16:34:19.977 | DEBUG | dask_remote_jobqueue.utils:_connection_ok:141 - [ConnectionManager][job_status: 4] 2022-02-22 16:34:19.978 | DEBUG | dask_remote_jobqueue.utils:_connection_ok:143 - [ConnectionManager][run][error: Scheduler Job exited with errors]
Contact Details
No response
What happened?
If the scheduler job exited with errors (e.g. job status = 4) the dask labextension still stry to connect instead reporting the creation error.
Version
v0.5.9 (Default)
What browsers are you seeing the problem on?
No response
Relevant log output
Code of Conduct