Which Celery task priority prevents synchronization race conditions during high-frequency commits?

Synchronization Concurrency in Weblate

Weblate employs a push‑pull mechanism via a Celery-based task queue to synchronize translation units between the PostgreSQL database and version control systems. In environments with high‑frequency commits, the asynchronous nature of these tasks can lead to a backlog or potential race conditions when multiple updates target the same component simultaneously.

When managing large‑scale projects, it is necessary to ensure that indexing and remote synchronization tasks are processed in a sequence that maintains data integrity without stalling the queue for other components.

• How does Weblate handle task prioritization for overlapping synchronization requests?
• Does the system implement a locking mechanism to prevent concurrent writes to the same translation file during a Celery task execution?