Deploying two builds at once doesn't lead to an error #309

New issue

Closed

opened 2026-06-18 14:15:54 +00:00 by ryansquared · 1 comment

ryansquared commented

2026-06-18 14:15:54 +00:00

(Migrated from codeberg.org)

An app being successfully deployed blocks successive git push. However, running git push twice leads to failure. This could be a TOCTOU on the db, but we need to ensure that we have an atomically acquired exclusive lock on the app before beginning a deployment.

An app being successfully deployed blocks successive `git push`. However, running `git push` twice leads to failure. This could be a TOCTOU on the db, but we need to ensure that we have an atomically acquired exclusive lock on the app before beginning a deployment.

vkobel commented

2026-07-01 13:10:00 +00:00

(Migrated from codeberg.org)

idx_eif_builds_active_app (unique partial index enforcing one active build per app) was added by Anton in 0c17178 on 2026-04-13 ("enforce only one build at a time for each app") and dropped by Ryan in 43d4eb4 on 2026-05-17 with no rationale.

Why'd it come out?

`idx_eif_builds_active_app` (unique partial index enforcing one active build per app) was added by Anton in 0c17178 on 2026-04-13 ("enforce only one build at a time for each app") and dropped by Ryan in 43d4eb4 on 2026-05-17 with no rationale. Why'd it come out?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

public/platform#309

No description provided.

Rows
Columns