Is your feature request related to a problem? Please describe.

Currently, the app is stateless – there is no knowledge about the state of the system as a whole. Because of it, one can't know what workers are currently running or cancel a job.

Describe the solution you'd like

I would like Repid apps to be able to communicate with each other, thus enabling many more features.

Is your feature request related to a problem? Please describe.
Actors aren't validating their input/output, I end up writing a lot of validation boilerplate.

Describe the solution you'd like
Integration with Pydantic - something like FastAPI does.

Describe alternatives you've considered
Integration with attrs/dataclasses/etc.: Pydantic is just the best match for this job.

Additional context
Will probably wait till Pydantic v2 release.

Documentation needs to be updated to v1.0.0.

Is your feature request related to a problem? Please describe.
I'm creating endpoints which usually has only one purpose: schedule some task, return its id, get task's result by id. This is repetitive and frustrating.

Describe the solution you'd like
FastAPI integration, which will autogenerate endpoints, something like FastAPI CRUD router does.

Describe alternatives you've considered
Writing everything by hand 🤣, not really an option

Additional context
Will need to make Pydantic integration first.

Is your feature request related to a problem? Please describe.

When running in some orchestrated environment, such as Kubernetes, it's important that the app reports its status to the orchestrator. Currently, doing so requires spinning up a separate web server and wrapping Repid application around it, which is very annoying.

Describe the solution you'd like

Repid should come with as simple web server, which will be able to answer health check requests.

Hello, Thanks for the library :)

I'm trying to create recuring job which would execute every N days. Looking at the docs I found this:
https://repid.aleksul.space/1.0.0rc3/user_guide/deferred_scheduling/

Example code i had in mind is:

from repid import Job
from repid.router import Router, RouterDefaults
import settings

router = Router(defaults=RouterDefaults(queue=settings.rmq_name))


@router.actor
async def delete_stuff_in_db():
    print("delete_stuff_in_db")


def enqueue_delete_stuff_in_db():
    await Job(
        "delete_stuff_in_db",
        settings.rmq_name,
        timeout=timedelta(seconds=30),
        deferred_by=timedelta(days=7)
    ).enqueue()


if __name__ == "__main__":
    enqueue_delete_stuff_in_db()

Would running this on single container start suffice, or is there something more I'm missing?
In case there are several instances of app running how would this behave. Would i need to make sure only one is running it?

Thanks in advance for help :)

Describe the bug

Consumer stops silently - can't be seen in RabbitMQ management interface and produces no logs.

To Reproduce

Produce BasicCancel from some other channel, rather than used for a consumer.

Expected behavior

Consumer tries to restart by emitting BasicConsume, otherwise produces an exception.

Info

• OS information - docker
• Repid version - v1.5.0

It should possible to use Repid with Kafka.
Idea is to introduce Kafka connection and to allow usage of pub/sub pattern via same Repid api as for the others.

Is this something which would be accepted?

Is your feature request related to a problem? Please describe.

I would like to have an automatically generated documentation to share with my colleagues in a form of AsyncAPI schema.

Describe the solution you'd like

Repid.Router should have some method to generate AsyncAPI schema for its actors.

Additional context

Ideally, the implementation will take advantage from type annotations in actors.

We need to regain 100% coverage!

Is your feature request related to a problem? Please describe.

Currently, Repid doesn't provide any utilities to make testing easier, nor any documentation on how to approach testing. It makes testing unnecessary complicated.

Describe the solution you'd like

Pytest fixtures/markers or generally any kind of testing utilities + documentation on how to approach testing.

Describe the bug
Repid icon from README.md on android mobile client doesn't change color.

To Reproduce

• Open android mobile github client
• Open the repository
• Scroll down code page to the README.md information

Expected behavior
Switching icon color to white on the dark theme of github client.

Screenshots

Versions:

• Android 9.0
• GitHub mobile v1.71.1
• Repid v1.0.0b7