Error 500 when creating new pull request #607

New Issue

GiteaMirror · 2025-11-02T03:29:47-06:00

GiteaMirror commented

2025-11-02 03:29:47 -06:00

Originally created by @tobias-- on GitHub (Apr 3, 2017).

Gitea version (or commit ref): 1.1.0
Git version:
Operating system: Windows 2008 R2
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant
Log gist:

2017/04/03 15:01:21 [T] PullRequest[0].testPatch (patchPath): E:\gogs-repositories\XXX\XXX.git\pulls\34.patch
2017/04/03 15:01:21 [T] NewMessageFrom (htmlBody):
[E-Mail contents]
2017/04/03 15:01:21 [T] New e-mail sending request [XXXX@XXX]: Subject: [XXX] XXXXX (#34), issue comment
2017/04/03 15:01:22 [T] PushToBaseRepo[7]: pushing commits to base repo 'refs/pull/34/head'
2017/04/03 15:01:22 [T] DeliverHooks [repo_id: 7]
2017/04/03 15:01:23 [T] E-mails sent [XXXX@XXX]: Subject: [XXX] XXXXXX (#34), issue comment
2017/04/03 15:01:24 [T] Pull request created: 7/45
2017/04/03 15:01:24 [D] Session ID: 69b660ffed886882
2017/04/03 15:01:24 [D] CSRF Token: eiBhxp_6MTDX7ZVZMbbfWgZRKP46MTQ5MTIwMTMyODYxMTk1NDgwMA==
2017/04/03 15:01:24 [...user/notification.go:33 GetNotificationCount()] [E] GetNotificationCount: database table is locked: notification
2017/04/03 15:01:24 [D] Template: status/500

Description

Creating a new PR will sometimes result in a 500 error. The PR seems to be alright and can be merged. It seems that updating notifications table does not work.

Originally created by @tobias-- on GitHub (Apr 3, 2017). - Gitea version (or commit ref): 1.1.0 - Git version: - Operating system: Windows 2008 R2 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: ``` 2017/04/03 15:01:21 [T] PullRequest[0].testPatch (patchPath): E:\gogs-repositories\XXX\XXX.git\pulls\34.patch 2017/04/03 15:01:21 [T] NewMessageFrom (htmlBody): [E-Mail contents] 2017/04/03 15:01:21 [T] New e-mail sending request [XXXX@XXX]: Subject: [XXX] XXXXX (#34), issue comment 2017/04/03 15:01:22 [T] PushToBaseRepo[7]: pushing commits to base repo 'refs/pull/34/head' 2017/04/03 15:01:22 [T] DeliverHooks [repo_id: 7] 2017/04/03 15:01:23 [T] E-mails sent [XXXX@XXX]: Subject: [XXX] XXXXXX (#34), issue comment 2017/04/03 15:01:24 [T] Pull request created: 7/45 2017/04/03 15:01:24 [D] Session ID: 69b660ffed886882 2017/04/03 15:01:24 [D] CSRF Token: eiBhxp_6MTDX7ZVZMbbfWgZRKP46MTQ5MTIwMTMyODYxMTk1NDgwMA== 2017/04/03 15:01:24 [...user/notification.go:33 GetNotificationCount()] [E] GetNotificationCount: database table is locked: notification 2017/04/03 15:01:24 [D] Template: status/500 ``` ## Description Creating a new PR will sometimes result in a 500 error. The PR seems to be alright and can be merged. It seems that updating notifications table does not work.

GiteaMirror added the type/bug label 2025-11-02 03:29:47 -06:00

GiteaMirror closed this issue

2025-11-02 03:29:48 -06:00

GiteaMirror commented

2025-11-02 03:29:48 -06:00

@plessbd commented on GitHub (Apr 3, 2017):

duplicate of #1372 ?

@plessbd commented on GitHub (Apr 3, 2017): duplicate of #1372 ?

GiteaMirror commented

2025-11-02 03:29:49 -06:00

@lunny commented on GitHub (Apr 3, 2017):

seems not.

@lunny commented on GitHub (Apr 3, 2017): seems not.

GiteaMirror commented

2025-11-02 03:29:49 -06:00

@plessbd commented on GitHub (Apr 3, 2017):

You are right, didnt fully see the end of error line.
Seem related though, both are because of a table lock.
This one on notification, #1372 because of repository

@plessbd commented on GitHub (Apr 3, 2017): You are right, didnt fully see the end of error line. Seem related though, both are because of a table lock. This one on `notification`, #1372 because of `repository`

GiteaMirror commented

2025-11-02 03:29:49 -06:00

@bkcsoft commented on GitHub (Jun 15, 2017):

Could you test if this fixes the issue? #1961 (applying the diff and building on v1.1.2 should be straight forward)

@bkcsoft commented on GitHub (Jun 15, 2017): Could you test if this fixes the issue? #1961 (applying the diff and building on v1.1.2 should be straight forward)

GiteaMirror commented

2025-11-02 03:29:49 -06:00

@lunny commented on GitHub (Jun 20, 2017):

@bkcsoft I think #1961 didn't resolve the database lock problem. And move all database lock issues to v1.3.

@lunny commented on GitHub (Jun 20, 2017): @bkcsoft I think #1961 didn't resolve the database lock problem. And move all database lock issues to v1.3.

GiteaMirror commented

2025-11-02 03:29:49 -06:00

@lunny commented on GitHub (Jun 23, 2017):

continue via #2040

@lunny commented on GitHub (Jun 23, 2017): continue via #2040

GiteaMirror referenced this issue

2025-11-02 11:47:37 -06:00

[PR #607] [MERGED] Add default SSH_LISTEN_PORT config value (#603) #15485

Sign in to join this conversation.