Florian Jetter

Worker stream comm error log only when in state running

2

This log message is also issued if the worker closes properly. That is a bit confusing. If this happens in a non-closing state, I consider this an error and promoted...

Reduce recursionlimit for `test_client.py::test_profile`

1

I don't really understand fully what's going on but we've seen some fatal windows errors on CI with this. This _should_ never happen since the merge actually catches a `RecursionError`...

Update CI stability

6

With a couple of recent merges, I triggered yesterday another "CI stress test" that runs our suite a couple of times in a row (this time 10) see https://github.com/fjetter/distributed/tree/stress_ci which...

Root-task withholding without co-assignment

1

We had an early attempt to experiment with root-task withholding to address the problem of root-task-overproduction. Below a couple of links with additional information (non-exhaustive) - https://github.com/dask/distributed/issues/6360 - https://github.com/dask/distributed/issues/5223 -...

Design and prototype for root-ish task deprioritization by withholding tasks on the scheduler

10

Root task overproduction is a significant problem for memory pressure and runtime https://github.com/dask/distributed/issues/6360 has shown that we can find a way to deal with the problem isolated in the scheduler...

This is an issue to track efforts towards some modernization efforts of our asyncio infrastructure. Very roughly this is about - Addressing all warnings triggered by py3.10 - Slowly migrating...

No longer start stopped loops in LoopRunner to allow the use of asyncio.run

11

The `LoopRunner` is accepting an event loop that has been created externally. This is a pattern that has been deprecated by CPython and our current implementation. ## Requirements - `LoopRunner`...

Disable profiler in tests?

5

We constantly have a profiler running in the background, often the threads associated to it are not properly cleaned up. In https://github.com/dask/distributed/pull/6033 we discovered that it can also be responsible...

Tornado 6.2 compatibility

3

Tornado 6.2 was just released and we're hitting a few errors on CI. So far, the only thing I observed was a deprecation warning that is converted to an error....

There's been a movement to switch the default branch from `master` to `main` to avoid possibly offensive nomenclature. There are also some official [docs from github about the topic](https://github.com/github/renaming).