spumer

finally we are fixed it by strict status transition flow: ```python class AdminMiddleware(django_dramatiq.middleware.AdminMiddleware): logger = logging.getLogger(__name__).getChild('AdminMiddleware') @cached_property def transitions(self): from django_dramatiq.models import Task # target_status -> [source_status, ...] transitions =...

@amureki if you agree with that i will make a PR

I think it's also depends on Exception type. And passing `(retries, exception)` to `backoff_factory` will also consistent with `retry_when` which already handle this parameters

We got something similiar with --process 1 --threads 2. When Worker consume one queue and produce messages to another. We reproduce it yesterday and will investigate what happend actually Quick...

I'm released thread-safe broker implemention https://github.com/spumer/dramatiq-kombu-broker/ We does not have hangs anymore with that

Works well with `kombu + rabbitmq`. Right now dramatiq-kombu-broker support only RabbitMQ

>Is there a way to check the current status of a Dramatiq task by its jobId? We solve it by https://github.com/Bogdanp/django_dramatiq, it has Task model and middleware which write message...

You need to implement manually. Dramatiq has no functionality to revoke task. I think it can be done by implement like in celery: create queue for events and dispatch events...

Without that fix we have incorrect behaviour in Retries middleware, when enqueue to DELAY queue failed we silently ACK message and lose it @Bogdanp

It's would not be redelivered since it's acked. Steps: - processing in actor failed - retry middleware try to delay (in `after_process_message` hook) - delay failed (in `after_process_message` hook) -...