Race condition in \Drupal\content_lock\ContentLock\ContentLock::locking() as we fetch the lock (select) and then separately create the lock (merge)

Created on 17 April 2024, 5 months ago
Updated 14 May 2024, 4 months ago

Problem/Motivation

We have a race condition in \Drupal\content_lock\ContentLock\ContentLock::locking() because the select and merge are separate queries.

Proposed resolution

Either use the lock service to wrap the select and merge in a lock or maybe code to do a merge without a select and then catch the failures when the lock exists already.

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡¬πŸ‡§United Kingdom alexpott πŸ‡ͺπŸ‡ΊπŸŒ

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024