[PR #2127] [CLOSED] [WIP] Fix SQLite 'database table is locked' problem #16245

New Issue

GiteaMirror · 2025-11-02T12:05:49-06:00

GiteaMirror commented

2025-11-02 12:05:49 -06:00

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/2127
Author: @typeless
Created: 7/8/2017
Status: ❌ Closed

Base: master ← Head: unlock_notify_test

📝 Commits (4)

89c84a3 Proof of concept
1410e1e Update
3dee8a3 Update
872ed88 Update

📊 Changes

3 files changed (+71 additions, -2 deletions)

View changed files

➕ vendor/github.com/mattn/go-sqlite3/callback.c (+5 -0)
📝 vendor/github.com/mattn/go-sqlite3/callback.go (+34 -0)
📝 vendor/github.com/mattn/go-sqlite3/sqlite3.go (+32 -2)

📄 Description

Fixes #2040

CAVEAT: the PR hasn't fixed the issue yet.

According to the documentation, the upper layer has to handle the SQLITE_LCOKED status code reported by the underlying sqlite_unlock_notify API as well. The proper approach to fix it in upper layers still needs investigation but the basic mechanism described in the following link has been implemented in the PR.

If this can eventually fix the issue, I will propose the PR to upstream.

Reference: https://sqlite.org/unlock_notify.html.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/2127 **Author:** [@typeless](https://github.com/typeless) **Created:** 7/8/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `unlock_notify_test` --- ### 📝 Commits (4) - [`89c84a3`](https://github.com/go-gitea/gitea/commit/89c84a35baae0df1fdf79012b364aa385800d041) Proof of concept - [`1410e1e`](https://github.com/go-gitea/gitea/commit/1410e1ea48d6d95a3d452523565c00b2e726d7f1) Update - [`3dee8a3`](https://github.com/go-gitea/gitea/commit/3dee8a3b163d4e96da83628f659423b98a5e8b2a) Update - [`872ed88`](https://github.com/go-gitea/gitea/commit/872ed885d0e6a508fa684167a8c974045d2136f1) Update ### 📊 Changes **3 files changed** (+71 additions, -2 deletions) <details> <summary>View changed files</summary> ➕ `vendor/github.com/mattn/go-sqlite3/callback.c` (+5 -0) 📝 `vendor/github.com/mattn/go-sqlite3/callback.go` (+34 -0) 📝 `vendor/github.com/mattn/go-sqlite3/sqlite3.go` (+32 -2) </details> ### 📄 Description Fixes #2040 CAVEAT: the PR hasn't fixed the issue yet. According to the documentation, the upper layer has to handle the `SQLITE_LCOKED` status code reported by the underlying `sqlite_unlock_notify` API as well. The proper approach to fix it in upper layers still needs investigation but the basic mechanism described in the following link has been implemented in the PR. If this can eventually fix the issue, I will propose the PR to upstream. Reference: https://sqlite.org/unlock_notify.html. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2025-11-02 12:05:49 -06:00

GiteaMirror closed this issue

2025-11-02 12:05:49 -06:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#16245