BR
BR
Hello, The only reason why celery5 is not stated as supported is - I never battle tested such combination. AFAIR when dyrygent was developed there was no celery 5 :octocat:...
I've removed some dust and I managed to successfully run integration tests against celery v5.2.7. That's a good sign.
Hello, Thanks for the report. This looks like a design flaw or a bug in dyrygent. I'll take a closer look into it once I have a spare moment.
So this issue is a limitation of current version of dyrygent. When chain `on_error` is defined as follows ``` chain1.on_error(callback.si(f"Leaf chain 1 failed")) ``` Celery does not immediately attach `on_error`...
I've slightly modified your last piece of code. ```python chain1 = chain( normal_task.si(), normal_task.si(), failing_task.si(), ) for task in chain1.tasks: task.on_error(callback.si("Leaf chain 1 failed")) wf = Workflow() wf.set_retry_policy("random", 1, 3)...
Hello, This is an expected behavior. I never needed this feature of celery and no one has ever requested it. Personally I find the injection of preceding task result as...
I'll see what I can do once I have some spare time.
Yup, that's the case https://github.com/golang/go/issues/47492
The funny thing is that mime type is properly set in the DB when upload is created through web GUI (browser sends file type in request body) ``` POST /upload...