Skip to content

fix(actions): handle MSSQL deadlock in runner job pickup - #39513

Open
silverwind wants to merge 2 commits into
go-gitea:release/v28from
silverwind:claim-deadlock-backport
Open

silverwind wants to merge 2 commits into
go-gitea:release/v28from
silverwind:claim-deadlock-backport

Conversation

@silverwind

@silverwind silverwind commented Oct 1, 2026 •

Copy link
Copy Markdown
Member

Minimal backport of #39512 which adds no migration.

SQL Server can pick the pickup scan as deadlock victim when it races a
concurrent claim, failing the runner's poll. Rerun the page on a fresh
session instead, since the index-based fix on main needs a migration
that can't go into a release branch.

Assisted-by: Claude Code:claude-opus-5-5
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Oct 1, 2026
@GiteaBot GiteaBot added this to the 29.0.0 milestone Oct 1, 2026
@github-actions github-actions Bot added topic/gitea-actions related to the actions of Gitea type/bug labels Oct 1, 2026
@silverwind silverwind modified the milestones: 29.0.0, 28.0.1 Oct 1, 2026
Only the deadlock rerun needs a fresh session, so the regular scan
keeps the session it already had.

Assisted-by: Claude Code:claude-opus-5-5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. topic/gitea-actions related to the actions of Gitea type/bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants