Dmitrii Anfimov

Try to use `ListRedisScheduleSource` instead of `RedisScheduleSource`: - `RedisScheduleSource` is [deprecated](https://github.com/taskiq-python/taskiq-redis/blob/18f9f4de5261cdcc3dc2f013a971c9c89fe3a2e3/taskiq_redis/schedule_source.py#L57) and will be removed in future releases; - As far as I know `ListRedisScheduleSource` has performance improvements in comparison...

I have the same problem. I tried subscribing to Zed Free hoping that would solve the problem. But the problem remains - only the warning that I am not subscribed...

Аналогичная проблема есть и в ручке получения информации о пользователе по login/uid: https://cloud.yandex.ru/docs/tracker/get-user Судя по всему, там тоже можно получить НЕ массив в ответе.

As far as I know, there’s currently no convenient way to run the scheduler and the worker at the same time. This is mainly because the worker and scheduler can...

This functionality has already been implemented in https://github.com/taskiq-python/taskiq/pull/498

I already created pull request for that issue: https://github.com/taskiq-python/taskiq-valkey/pull/1 So after review it will be possible to use taskiq-valkey in a similar way as taskiq-redis.

Maybe it will be even better to migrate from `setup.py` completely and use `pyproject.toml` with `build` instead: - https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html - https://build.pypa.io/en/stable/ But let's think about it in a different MR...

After some more hours of debug I decided to switch to [uv](https://docs.astral.sh/uv/) and [hatch](https://hatch.pypa.io/latest/) for package build. Now it should work. You can test build process like that: - Delete...

It looks like the original question has been answered. So I'll close this issue.