django-q
django-q copied to clipboard
A multiprocessing distributed task queue for Django
Basically when you write your Schedule in models.py, you won't be able to migrate or makemigrations when you run a fresh app from github, any idea how to solve that?
Hi, I'm using Django Q (latest version) the following way (Django 3.0.2, Python 3.7.5): `Schedule.objects.create(func='......', args=1, repeats = -1, schedule_type=Schedule.WEEKLY, next_run=start_activate) ` In Sentry, I am receiving a lot of...
Hi, I'm looking for a function/s in the Django-q which can be used that satisfies below requirements: - Able to fire multiple tasks (long running) asynchronously - Able to stop...
django-q version 1.3.8: ``` $ poetry show django-q name : django-q version : 1.3.8 description : A multiprocessing distributed task queue for Django dependencies - arrow >=1.1.0,=1.17.6,=2.2 - django-picklefield >=3.0.1,=3.5.3,
I started using Django Q today as an alternative to Celery, so that I wouldn't have to use redis for my extremely simple project that only needs to do an...
Hi, We're getting bad performance when the below query is executed every 30s. Could you please tell me if we can have any indexes in the table `django_q_schedule`? (Because the...
We have a working django-q setup with the following config: ``` Q_CLUSTER = { "orm": "default", "timeout": 60, 'attempt_count': 1 "max_attempts": 2, "retry": 120, "catch_up": False, "workers": 1, "ack_failures": True...
Hi again @Koed00 I'd like to add `retry` to opt_keys in `async_task`. We have implemented our own custom ORM broker that makes use of custom retry value like this: ```python...
If you fork the repository and run the GitHub actions without actually changing anything, you get the following error: ``` • Installing iron-core (1.2.0): Failed EnvCommandError Command ['/root/.cache/pypoetry/virtualenvs/django-q-9TtSrW0h-py3.8/bin/pip', 'install', '--no-deps',...
`async_ = Iter(recognize) async_.append(1) async_.run()` This always leads to a > [Q] ERROR No ":" found in value which is raised by the core.signing module in the unsign-method. I found...