Jonathan Miller
dd6fc4b69c
When multiple workflows are triggered by a single event (e.g. a pull_request with several matching workflow files), each InsertRun transaction acquires an X-lock on the repository row via UpdateRepoRunsNumbers and an index lock on action_run. Two concurrent transactions can deadlock when each holds one lock and waits for the other. InnoDB kills the lighter transaction, but handleWorkflows only logged the error and silently dropped the workflow run — making it appear as though pull_request events were never fired. This was the root cause of API-created PRs appearing to not trigger Actions workflows: the notification pipeline was correct, but the DB insert was lost to an unretried deadlock. The fix wraps PrepareRunAndInsert in a retry loop (up to 3 attempts with exponential backoff) that detects deadlock errors across MySQL, PostgreSQL, and SQLite. On deadlock, the rolled-back run fields are reset before the next attempt. Also adds db.IsErrDeadlock() for cross-engine deadlock detection and unit tests for the same. Closes #220 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
MokoGitea
Moko fork of Gitea — adding project board REST API endpoints and custom enhancements
Custom Gitea fork with Project Board API
Pages
- Branding
- Deployment
- [Project API](Project API)
- roadmap
Category: Infrastructure | Platform: moko-platform wiki
Documentation
Full documentation is available on the Wiki.
Contributing
See the wiki for development guidelines and contribution instructions.
License
This project is licensed under the GNU General Public License v3.0 or later -- see the LICENSE file.