distributed good first issues (Python)

Include `Worker._missing_dep_flight` in cluster dumps 11 days ago

enhancement good first issue diagnostics stability

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

High CPU usage when idle, possibly DNS related about 1 month ago

bug help wanted windows

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Client.submit *args is typehinted wrongly 2 months ago

bug help wanted good first issue

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Documentation / type hinting for `Future.status` 4 months ago

good first issue typing

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Dask worker CLI error message might be misleading 5 months ago

enhancement good first issue p3

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Client.scheduler_info needs better documentation 7 months ago

documentation good first issue

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

`retry` can produce excessively large logs 8 months ago

enhancement good first issue

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Docstring for `Scheduler.close` refers to non-existent `Scheduler.cleanup` method 8 months ago

bug documentation good first issue

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Total CPU % on /workers tab makes little sense 8 months ago

good first issue diagnostics dashboard

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Add Semaphore, Condition, Event 11 months ago

good first issue

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

documentation not updated following #3029 12 months ago

help wanted documentation

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

check if a Plugin is present about 1 year ago

enhancement help wanted good first issue

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

Allow renaming worker ThreadPool's thread_name_prefix from worker parameters about 1 year ago

enhancement help wanted

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

"TypeError: h5py objects cannot be pickled" when applying map_blocks to dask array constructed from HDF5 dataset about 1 year ago

bug help wanted

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

`/metrics` sometimes miss dask specific metrics over 1 year ago

AI Summary: The task is to debug a Dask distributed scheduler issue where the `/metrics` endpoint sometimes fails to expose Dask-specific metrics (e.g., `dask_*` metrics) when using Prometheus for monitoring. The problem seems to be related to timing; querying the endpoint before the worker is fully initialized results in missing metrics. The solution involves investigating the timing dependency between worker initialization and metric exposure, potentially adjusting the logic to ensure metrics are available consistently.

Complexity: 4/5

bug help wanted

dask/distributed

1.7K

A distributed task scheduler for Dask

Python

#dask#distributed-computing#pydata#python

dask/distributed

Open Issues Need Help