Skip to main content

Browse the archive

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 
Fix issues related to rq job dependencies (#7139)
 
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
Raw File
SECURITY.md 
# Security Policy

## Supported Versions

At the moment only the latest release is supported. When you report a security issue,
be sure it can be reproduced in the supported version.

| Version | Supported          |
| ------- | ------------------ |
| 2.0.0   | :white_check_mark: |
| <2.0.0  | :x:                |

## Reporting a Vulnerability

If you have information about a security issue or vulnerability in the product, please
send an e-mail to [secure@cvat.ai](mailto:secure+github@cvat.ai).

Please provide as much information as possible, including:

- The products and versions affected
- Detailed description of the vulnerability
- Information on known exploits
- A member of the CVAT.ai Product Security Team will review your e-mail and contact you to
  collaborate on resolving the issue.
back to top