Somethimes when you modify tags for a existent issue, 2 tags will be added/removed and one no (or something like that) #4716

New Issue

GiteaMirror · 2025-11-02T06:00:40-06:00

GiteaMirror commented

2025-11-02 06:00:40 -06:00

Originally created by @BaxAndrei on GitHub (Jan 24, 2020).

Gitea version (or commit ref): 1.11.0-rc2
Git version: 2.23.0
Operating system: Centos 7 x64
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: -

Description

I think the attached video already explains everything about this issue.
...

Screenshots

https://youtu.be/fFSwtwnwzOs

Originally created by @BaxAndrei on GitHub (Jan 24, 2020). - Gitea version (or commit ref): 1.11.0-rc2 - Git version: 2.23.0 - Operating system: Centos 7 x64 - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [] Yes (provide example URL): - [x] No - [ ] Not relevant - Log gist: - ## Description I think the attached video already explains everything about this issue. ... ## Screenshots https://youtu.be/fFSwtwnwzOs

GiteaMirror added the issue/stale label 2025-11-02 06:00:40 -06:00

GiteaMirror closed this issue

2025-11-02 06:00:40 -06:00

GiteaMirror commented

2025-11-02 06:00:41 -06:00

@bagasme commented on GitHub (Jan 25, 2020):

@baxandrei Tag consistency?

@bagasme commented on GitHub (Jan 25, 2020): @baxandrei Tag consistency?

GiteaMirror commented

2025-11-02 06:00:41 -06:00

@lunny commented on GitHub (Jan 25, 2020):

@baxandrei any error logs?

@lunny commented on GitHub (Jan 25, 2020): @baxandrei any error logs?

GiteaMirror commented

2025-11-02 06:00:41 -06:00

@guillep2k commented on GitHub (Jan 25, 2020):

Sounds to me like an async info serialization problem. I didn't get to see much of the code, but is it possible that labels are being sent from the broswer as an array (ReplaceIssueLabels) instead of one by one (AddIssueLabels, DeleteIssueLabel)? Or perhaps the response from the server replaces the working set in the browser. If that's the case, multiple requests in parallel may contain outdated information if previous requests haven't resolved yet.

@guillep2k commented on GitHub (Jan 25, 2020): Sounds to me like an async info serialization problem. I didn't get to see much of the code, but is it possible that labels are being sent from the broswer as an array (`ReplaceIssueLabels`) instead of one by one (`AddIssueLabels`, `DeleteIssueLabel`)? Or perhaps the response from the server replaces the working set in the browser. If that's the case, multiple requests in parallel may contain outdated information if previous requests haven't resolved yet.

GiteaMirror commented

2025-11-02 06:00:41 -06:00

@BaxAndrei commented on GitHub (Jan 25, 2020):

@baxandrei any error logs?

[Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 500 Internal Server Error in 99.347423ms
[Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 500 Internal Server Error in 91.280944ms
[Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 500 Internal Server Error in 99.58221ms
[Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 200 OK in 106.212736ms

2020/01/25 19:32:52 .../xorm/session_raw.go:180:exec() [I] [SQL] UPDATE `issue` SET `updated_unix` = ? WHERE `id`=? []interface {}{1579973572, 77} - took: 50.399024ms
2020/01/25 19:32:52 .../repo/issue_label.go:166:UpdateIssueLabel() [E] AddLabel: Error 1213: Deadlock found when trying to get lock; try restarting transaction

@BaxAndrei commented on GitHub (Jan 25, 2020): > @baxandrei any error logs? ``` [Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 500 Internal Server Error in 99.347423ms [Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 500 Internal Server Error in 91.280944ms [Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 500 Internal Server Error in 99.58221ms [Macaron] 2020-01-25 19:32:52: Completed POST /BaxAndrei/test/issues/labels 200 OK in 106.212736ms ``` ``` 2020/01/25 19:32:52 .../xorm/session_raw.go:180:exec() [I] [SQL] UPDATE `issue` SET `updated_unix` = ? WHERE `id`=? []interface {}{1579973572, 77} - took: 50.399024ms 2020/01/25 19:32:52 .../repo/issue_label.go:166:UpdateIssueLabel() [E] AddLabel: Error 1213: Deadlock found when trying to get lock; try restarting transaction ```

GiteaMirror commented

2025-11-02 06:00:42 -06:00

@bagasme commented on GitHub (Jan 26, 2020):

@baxandrei Please also post logs that lead to 500 error above.

@bagasme commented on GitHub (Jan 26, 2020): @baxandrei Please also post logs that lead to `500` error above.

GiteaMirror commented

2025-11-02 06:00:42 -06:00

@BaxAndrei commented on GitHub (Jan 26, 2020):

Where I can find these logs? related to error?

@BaxAndrei commented on GitHub (Jan 26, 2020): Where I can find these logs? related to error?

GiteaMirror commented

2025-11-02 06:00:42 -06:00

@stale[bot] commented on GitHub (Mar 26, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (Mar 26, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:00:42 -06:00

@stale[bot] commented on GitHub (May 25, 2020):

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale[bot] commented on GitHub (May 25, 2020): This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

GiteaMirror commented

2025-11-02 06:00:42 -06:00

@stale[bot] commented on GitHub (Jun 9, 2020):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Jun 9, 2020): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror referenced this issue

2025-11-02 13:34:44 -06:00

[PR #4716] [MERGED] Give user a link to create PR after push #17471

Sign in to join this conversation.