Revision 6e32868127bf0c51e49efabf8b68ad544cae9a3c authored by Maria Khrustaleva on 01 December 2023, 12:05:17 UTC, committed by GitHub on 01 December 2023, 12:05:17 UTC
This PR resolves 2 issues related to rq jobs: 1. In some scenarios it is possible to reach a situation when `X2` rq job depends on `X1` -> running `X1` job is moved to FailedJobRegistry and not deleted -> user creates one more `X1` job that is enqueued after `X2` execution. It was possible due to the second issue when a user tried to export annotations for task 1, then for task 2, and after restarting the worker container user tried again to export annotations for task 1. (cyclic dependence) 2. Looks like in rq implementation rq jobs that depend on `X` job will never be enqueued when `X` is moved to FailedJobRegistry due to AbandonedJobError. I've submitted the [issue](https://github.com/rq/rq/issues/2006) to the rq repository.
1 parent 81e88e1
File | Mode | Size |
---|---|---|
apps | ||
requirements | ||
settings | ||
utils | ||
__init__.py | -rw-r--r-- | 191 bytes |
asgi.py | -rw-r--r-- | 1011 bytes |
nginx.conf | -rw-r--r-- | 1.7 KB |
rq_patching.py | -rw-r--r-- | 3.0 KB |
rqworker.py | -rw-r--r-- | 2.0 KB |
schema.yml | -rw-r--r-- | 266.9 KB |
urls.py | -rw-r--r-- | 1.9 KB |
Computing file changes ...