Merge branch 'master' into feature/use-app-dir-to-specify-sources-directory

Author: s3rius

docs/available-components/brokers.md

@@ -82,7 +82,8 @@ await my_task.kicker().with_broker(broker).kiq()
 
 ## Custom brokers
 
-These brokers are not parts of the core taskiq lib. You can install them as a separate packages.
+These brokers are not parts of the core Taskiq lib. But they are maintained by Taskiq developers.
+You can install them as a separate packages.
 
 You can read more about parameters and abilities of these brokers in README.md of each repo.
 
@@ -110,3 +111,33 @@ Project link: [taskiq-nats](https://github.com/taskiq-python/taskiq-nats).
 ```bash
 pip install taskiq-nats
 ```
+
+## Third-party brokers
+
+These brokers are not part of the core Taskiq library. They are maintained by other open‑source contributors. You can install them as a separate packages.
+
+You can read more about parameters and abilities of these brokers in README.md of each repo.
+
+### PostgreSQL broker
+
+Project link: [taskiq-postgresql](https://github.com/z22092/taskiq-postgresql).
+
+```bash
+pip install taskiq-postgresql
+```
+
+### SQS broker
+
+Project link: [taskiq-aio-sqs](https://github.com/vonsteer/taskiq-aio-sqs).
+
+```bash
+pip install taskiq-aio-sqs
+```
+
+### YDB broker
+
+Project link: [taskiq-ydb](https://github.com/danfimov/taskiq-ydb).
+
+```bash
+pip install taskiq-ydb
+```

docs/available-components/result-backends.md

@@ -10,19 +10,60 @@ This includes:
 - return value;
 - Execution time in seconds.
 
-## DummyResultBackend
+## Built-in result backends
+
+### DummyResultBackend
 
 This result backend doesn't do anything. It doesn't store results and cannot be used in cases,
 where you need actual results.
 
 This broker will always return `None` for any return_value. Please be careful.
 
-## Redis result backend
 
-This result backend is not part of the core taskiq library. You can install it as a separate package [taskiq-redis](https://pypi.org/project/taskiq-redis/).
+## Official result backends
+
+This result backends is not part of the core Taskiq library. But they are maintained by Taskiq developers. You can install them as a separate package.
+
+### Redis result backend
+
+Project link: [taskiq-redis](https://pypi.org/project/taskiq-redis/).
 
 ```bash
 pip install taskiq-redis
 ```
 
-You can read more about parameters and abilities of this broker in [README.md](https://github.com/taskiq-python/taskiq-redis).
+### NATS result backend
+
+Project link: [taskiq-nats](https://github.com/taskiq-python/taskiq-nats).
+
+```bash
+pip install taskiq-nats
+```
+
+## Third-party result backends
+
+These result backends are not part of the core Taskiq library. They are maintained by other open‑source contributors. You can install them as a separate packages.
+
+### PostgreSQL result backend
+
+Project link: [taskiq-postgresql](https://github.com/z22092/taskiq-postgresql).
+
+```bash
+pip install taskiq-postgresql
+```
+
+### S3 result backend
+
+Project link: [taskiq-aio-sqs](https://github.com/vonsteer/taskiq-aio-sqs).
+
+```bash
+pip install taskiq-aio-sqs
+```
+
+### YDB result backend
+
+Project link: [taskiq-ydb](https://github.com/danfimov/taskiq-ydb).
+
+```bash
+pip install taskiq-ydb
+```

docs/available-components/schedule-sources.md

@@ -5,9 +5,12 @@ order: 4
 # Available schedule sources
 
 These objects are used to fetch current schedule for tasks.
-Currently we have only one schedule source.
 
-## RedisScheduleSource
+## Official schedule sources
+
+These schedule sources are not part of the core Taskiq library. But they are maintained by Taskiq developers. You can install them as a separate package.
+
+### RedisScheduleSource
 
 This source is capable of adding new schedules in runtime. It uses Redis as a storage for schedules.
 To use this source you need to install `taskiq-redis` package.
@@ -24,7 +27,7 @@ scheduler = TaskiqScheduler(broker, sources=[redis_source])
 For more information on how to use dynamic schedule sources read [Dynamic scheduling section](../guide/scheduling-tasks.md#dynamic-scheduling).
 
 
-## LabelScheduleSource
+### LabelScheduleSource
 
 This source parses labels of tasks, and if it finds a `schedule` label, it considers this task as scheduled.
 
@@ -34,12 +37,13 @@ The format of the schedule label is the following:
 @broker.task(
     schedule=[
         {
-            "cron": "* * * * *", # type: str, either cron or time should be specified.
+            "cron": "*/1 * * * *", # type: str, either cron or time should be specified.
             "cron_offset": None # type: str | timedelta | None, can be omitted.
             "time": None  # type: datetime | None, either cron or time should be specified.
             "args": [], # type List[Any] | None, can be omitted.
             "kwargs": {}, # type: Dict[str, Any] | None, can be omitted.
             "labels": {}, # type: Dict[str, Any] | None, can be omitted.
+            "schedule_id": "every_minute",  # type: str | None, can be omitted.
         }
     ]
 )
@@ -55,6 +59,7 @@ Parameters:
 - `args` - args to use, when invoking the task.
 - `kwargs` - key-word arguments to use when invoking the task.
 - `labels` - additional labels to use when invoking the task.
+- `schedule_id` - unique identifier of the schedule. If not specified, a random uuid will be generated.
 
 To enable this source, just add it to the list of sources:
 
@@ -76,3 +81,43 @@ In order to resolve all labels correctly, don't forget to import
 all task modules using CLI interface.
 
 :::
+
+### NATS schedule source
+
+This source is capable of adding new schedules in runtime. It uses NATS as a storage for schedules.
+To use this source you need to install `taskiq-nats` package.
+
+```python
+from taskiq_nats import NATSKeyValueScheduleSource
+from taskiq.scheduler import TaskiqScheduler
+
+
+broker = ...
+
+scheduler = TaskiqScheduler(
+    broker=broker,
+    sources=[NATSKeyValueScheduleSource(broker)],
+)
+```
+
+This schedule source doesn't use `schedule` label on tasks. To add new schedules, you need to call `add_schedule` method on the source.
+
+## Third-party schedule sources
+
+These schedule sources are not part of the core Taskiq library. They are maintained by other open‑source contributors. You can install them as a separate packages.
+
+### PostgreSQL schedule source
+
+Project link: [taskiq-postgres](https://github.com/danfimov/taskiq-postgres)
+
+```bash
+pip install taskiq-postgres
+```
+
+### YDB schedule source
+
+Project link: [taskiq-ydb](https://github.com/danfimov/taskiq-ydb)
+
+```bash
+pip install taskiq-ydb
+```

docs/extending-taskiq/schedule-sources.md

@@ -12,3 +12,8 @@ Here's a minimal example of a schedule source:
 @[code python](../examples/extending/schedule_source.py)
 
 You can implement a schedule source that write schedules in the database and have delayed tasks in runtime.
+
+::: info Cool tip!
+You can also use `LabelScheduleSource` as a base class for your schedule source
+if you want to parse schedules from task labels and don't want to implement logic for this from scratch.
+:::

docs/guide/README.md

@@ -21,18 +21,18 @@ We created this project because we couldn't find any project that can execute an
 
 You might have seen projects built on top of asyncio that solve a similar problem, but here's a comparison table of the taskiq and other projects.
 
-|                Feature name | Taskiq |  Arq  | AioTasks |
-| --------------------------: | :----: | :---: | :------: |
-|         Actively maintained |   ✅    |   ✅   |    ❌     |
-|    Multiple broker backends |   ✅    |   ❌   |    ✅     |
-|    Multiple result backends |   ✅    |   ❌   |    ❌     |
-|  Have a rich documentation  |   ✅    |   ❌   |    ❌     |
-|   Startup & Shutdown events |   ✅    |   ✅   |    ❌     |
-| Have ability to abort tasks |   ❌    |   ✅   |    ❌     |
-|          Custom serializers |   ✅    |   ✅   |    ❌     |
-|        Dependency injection |   ✅    |   ❌   |    ❌     |
-|              Task pipelines |   ✅    |   ✅   |    ❌     |
-|              Task schedules |   ✅    |   ✅   |    ❌     |
-|          Global middlewares |   ✅    |   ❌   |    ❌     |
+|                Feature name | Taskiq |  Arq  | AioTasks | streaQ |
+| --------------------------: | :----: | :---: | :------: | :----: |
+|         Actively maintained |   ✅    |   ✅   |    ❌     |   ✅   |
+|    Multiple broker backends |   ✅    |   ❌   |    ✅     |   ❌   |
+|    Multiple result backends |   ✅    |   ❌   |    ❌     |   ❌   |
+|  Have a rich documentation  |   ✅    |   ❌   |    ❌     |   ✅   |
+|   Startup & Shutdown events |   ✅    |   ✅   |    ❌     |   ✅   |
+| Have ability to abort tasks |   ❌    |   ✅   |    ❌     |   ✅   |
+|          Custom serializers |   ✅    |   ✅   |    ❌     |   ✅   |
+|        Dependency injection |   ✅    |   ❌   |    ❌     |   ❌   |
+|              Task pipelines |   ✅    |   ✅   |    ❌     |   ✅   |
+|              Task schedules |   ✅    |   ✅   |    ❌     |   ✅   |
+|          Global middlewares |   ✅    |   ❌   |    ❌     |   ✅   |
 
 If you have a fully synchronous project, consider using celery or dramatiq instead.

docs/guide/testing-taskiq.md

@@ -161,10 +161,7 @@ In such a way you don't need to manually call the `wait_result` in your code.
 To set it up, define the broker as the following:
 
 ```python
-...
-    broker = InMemoryBroker(await_inplace=True)
-...
-
+broker = InMemoryBroker(await_inplace=True)
 ```
 
 With this setup all `await function.kiq()` calls will behave similarly to `await function()`, but