Do not retry processing when there is no picture #199
Conversation
amureki
force-pushed
the
do-not-retry-when-no-file
branch
from
bf23124 to
3c5cba4
Compare
amureki
force-pushed
the
do-not-retry-when-no-file
branch
from
3c5cba4 to
2a3dbd6
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #199 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 13 13
Lines 496 496
=========================================
Hits 496 496
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
pictures/tasks.py
Outdated
| except FileNotFoundError: | ||
| # The file no longer exists (for example, because it was deleted or replaced). | ||
| return |
There was a problem hiding this comment.
Just silently ignoring missing files, will make it challenging to debug potential errors. I believe all message queues we use have a native behavior to fail without retrying on explicit exceptions. I'd recommend exploring that route.
There was a problem hiding this comment.
@codingjoe hm, this is a good suggestion!
I am struggling with figuring out the good way of doing so in django-rq (the interface is quite different from what I used to see in the other queues).
I added an example commit of how I see it with celery and dramatiq:
7c73c82
There was a problem hiding this comment.
I don't have much experience with RQ either, let's ask @krtko1
Do you have any idea how to solve this in RQ?
There was a problem hiding this comment.
@amureki my search only brought up this https://github.com/rq/rq/pull/1480/files
amureki
force-pushed
the
do-not-retry-when-no-file
branch
from
acc5822 to
7c73c82
Compare
This comes as an outcome of discussion #182