Assigning a PR causes the server to hang #2709

New Issue

GiteaMirror · 2025-11-02T04:45:13-06:00

GiteaMirror commented

2025-11-02 04:45:13 -06:00

Originally created by @apricote on GitHub (Jan 4, 2019).

Gitea version (or commit ref): v1.7.0-rc1, 5a1ea37
Git version: 2.17.1
Operating system: Ubuntu 16.04
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL) https://try.gitea.io/apricote/rebase-conflict/pulls/1
- No
- Not relevant
Log gist: https://gist.github.com/apricote/4cfb8b63feac29bdf85ab0be224f59bd

Description

Summary

When assigning a user to a PR, Gitea will never complete the POST request, from now on the Gitea Instance is "broken" and will not answer most requests. Restarting the server solves the problem until a user is assigned to a PR again.

The Log shows incoming requests, but they never succeed/complete:

[Macaron] 2019-01-04 17:26:12: Started POST /organization1/repository2/issues/assignee for 172.18.0.1
[Macaron] 2019-01-04 17:26:12: Started GET /organization1/repository2/pulls/42 for 172.18.0.1

Some requests still complete, for example, our instance is configured to require a login, accessing the PR page from an incognito browser window redirects me to the login page and renders it.

Steps to reproduce

Initially, the error happened in our company instance. I was able to reproduce the error on try.gitea.io.

Access a PR in the Web Interface (example https://try.gitea.io/apricote/rebase-conflict/pulls/1).
Change Assignee of PR and add a user.
Click outside of the Assignee window to send the request.
The request will never complete, the site is stuck in loading

Originally created by @apricote on GitHub (Jan 4, 2019).  - Gitea version (or commit ref): `v1.7.0-rc1`, 5a1ea37 - Git version: `2.17.1` - Operating system: Ubuntu 16.04 - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL) https://try.gitea.io/apricote/rebase-conflict/pulls/1 - [ ] No - [ ] Not relevant - Log gist: https://gist.github.com/apricote/4cfb8b63feac29bdf85ab0be224f59bd ## Description ### Summary When assigning a user to a PR, Gitea will never complete the `POST` request, from now on the Gitea Instance is "broken" and will not answer most requests. Restarting the server solves the problem until a user is assigned to a PR again. The Log shows incoming requests, but they never succeed/complete: ``` [Macaron] 2019-01-04 17:26:12: Started POST /organization1/repository2/issues/assignee for 172.18.0.1 [Macaron] 2019-01-04 17:26:12: Started GET /organization1/repository2/pulls/42 for 172.18.0.1 ``` Some requests still complete, for example, our instance is configured to require a login, accessing the PR page from an incognito browser window redirects me to the login page and renders it. ### Steps to reproduce Initially, the error happened in our company instance. I was able to reproduce the error on try.gitea.io. * Access a PR in the Web Interface (example https://try.gitea.io/apricote/rebase-conflict/pulls/1). * Change Assignee of PR and add a user. * Click outside of the Assignee window to send the request. * The request will never complete, the site is stuck in loading

GiteaMirror added the type/bug label 2025-11-02 04:45:13 -06:00

GiteaMirror closed this issue

2025-11-02 04:45:13 -06:00

GiteaMirror commented

2025-11-02 04:45:14 -06:00

@zeripath commented on GitHub (Jan 4, 2019):

OK this looks like an sqlite deadlock bug - I suspect the issue is at:

https://github.com/go-gitea/gitea/blob/master/models/issue_assignees.go#L176

@zeripath commented on GitHub (Jan 4, 2019): OK this looks like an sqlite deadlock bug - I suspect the issue is at: https://github.com/go-gitea/gitea/blob/master/models/issue_assignees.go#L176

GiteaMirror commented

2025-11-02 04:45:14 -06:00

@lafriks commented on GitHub (Jan 4, 2019):

I would not recommend running company instance on sqlite but @zeripath mentioned issue could be the cause

@lafriks commented on GitHub (Jan 4, 2019): I would not recommend running company instance on sqlite but @zeripath mentioned issue could be the cause

GiteaMirror commented

2025-11-02 04:45:14 -06:00

@pixelspark commented on GitHub (Oct 29, 2019):

Experiencing this as well but on 1.9.4 (also SQLite). Can I help in any way (e.g. where to look for logs?)

@pixelspark commented on GitHub (Oct 29, 2019): Experiencing this as well but on 1.9.4 (also SQLite). Can I help in any way (e.g. where to look for logs?)

GiteaMirror commented

2025-11-02 04:45:14 -06:00

@lunny commented on GitHub (Oct 30, 2019):

@pixelspark Please open another issue and give some details.

@lunny commented on GitHub (Oct 30, 2019): @pixelspark Please open another issue and give some details.

GiteaMirror referenced this issue

2025-11-02 12:13:13 -06:00

[PR #2709] [MERGED] Fix activity locale #16550

Sign in to join this conversation.