django-q2 icon indicating copy to clipboard operation
django-q2 copied to clipboard

A multiprocessing distributed task queue for Django based on Django-Q

Results 56 django-q2 issues
Sort by recently updated
recently updated
newest added

Hello, First, thank you for the project, very helpful. I am trying to have scheduled task in a CRON setup to have a timezone attached. Example : "30 8 *...

Hello, I've been using django-q2 on my first ever django project, been a treat so far, so much easier to setup than celery, thanks for this package! I have a...

I can this error when trying to use django-q2 package when sending emails: ``` INFO 2024-04-06 14:33:40,148 worker 22676 127007069675520 Process-0b549de9691d49f9b9dd40206f0ff9cf processing delaware-uranus-lemon-seventeen '' [email] Traceback (most recent call last):...

https://github.com/django-q2/django-q2/blob/1d1d0a9aa5332a68720d2423bd05c33290666cd6/django_q/pusher.py#L65 https://github.com/django-q2/django-q2/blob/1d1d0a9aa5332a68720d2423bd05c33290666cd6/django_q/worker.py#L57 The `task_queue` here extends `multiprocessing.queues.Queue`, which will **pick the x in `put()`** and **unpick x in `get()`**. This will spend seconds of time. See https://docs.python.org/3/library/multiprocessing.html#pipes-and-queues: > **Note** When...

To fix #180 , this approach it's mainly added by @germancollado

This fixes the #66 issue, it's happening because on windows the `ctrl+c` signal propagates over all subprocess (like pressing `ctrl+c` on each subprocess), then the sentinel will see that the...

Timeouts that happened with brokers that need acknowledging could have jobs that would keep retrying. This was caused due to the process being killed without sending the job back to...

Hi, I don't know if I'm missing something here but I haven't found a way to disable retry for all or a specific task. Let's consider the following (contrived) configuration:...

https://github.com/django-q2/django-q2/blob/7add68f7709856f875bf145d59374adc80112009/django_q/cluster.py#L317 Is there a reason why the cluster command's schedule processing is locked at running once every 30 seconds? I have scheduled tasks that need to run between that range...

i found in my task code, sometime is successful ,but i find error frequently, it show me task function is not defined in my mac m3. i have no idea...