Make Annotation more robust - AnnotationRangeLock unique_together
Open
- Dominant language
- Python
- Stars
- 30
- Forks
- 3
- Avg merge
- 9h 28m
- Merged PRs (30d)
- 42
Description
Split from SACGF/variantgrid_shariant#177
* Management command to deal with AnnotationRun dupes? Or just rely on it being fixed manually?
* Add unique_together database constraint on AnnotationRangeLock (and timestamps)
* Change celery routing - maybe even make a deployment check that makes sure the paths there are correct - may catch other problems this way (kinda lame Celery doesn't do this)
*
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.