Skip to content

Fixes #9: Prevent deadlocks between activation and bulk edits - #61

Merged
jnovinger merged 1 commit into
mainfrom
9-concurrent-activation-and-script-bulk-edits-can-deadlock
Oct 29, 2026
Merged

jnovinger merged 1 commit into
mainfrom
9-concurrent-activation-and-script-bulk-edits-can-deadlock

Conversation

@pheus

@pheus pheus commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

Fixes: #9

Activation and bulk edits through the UI and REST API now lock Scripts in a consistent primary-key order. Ordinary Script saves also avoid locking the parent Project.

Adds regression tests for lock order and scope while preserving the initial bulk edit confirmation page’s default ordering.

Activation now locks every Script of its Project in primary-key order
before it writes. The UI bulk edit and the REST bulk update save
Scripts in the same order. A Script save now locks only its own row,
not the Project row.

Fixes #9
@pheus
pheus marked this pull request as ready for review October 28, 2026 22:58
@pheus
pheus requested a review from jnovinger October 28, 2026 22:58
@jnovinger
jnovinger merged commit dbd0c8c into main Oct 29, 2026
20 checks passed
@jnovinger
jnovinger deleted the 9-concurrent-activation-and-script-bulk-edits-can-deadlock branch October 29, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Concurrent activation and Script bulk edits can deadlock

2 participants