Same issue shows twice in project's column

[stuzer05]

Description

I added spent time and then closed an issue

Gitea Version

trunk

Can you reproduce the bug on the Gitea demo site?

Yes

Log Gist

No response

Screenshots

Git Version

6c501b1

Operating System

No response

How are you running Gitea?

binary

Database

None

[edlerd]

I would like to work on this, can you assign me?

[stuzer05]

I would like to work on this, can you assign me?

You can make a pr, I don't have rights to assign anyone

[edlerd]

Can you reproduce the bug on the Gitea demo site?

Yes

@stuzer05 can you please add detailed steps how to reproduce the issue on https://try.gitea.io/ ?
I am having trouble finding a way to reproduce it.

[stuzer05]

I honestly cannot reproduce it myself, it was just random. The problem was in the project_issue table thewe were 2 identical records. Maybe, if there was a constraint for unique column values there wouldn't be an issue

[techknowlogick]

@stuzer05 which database are you using?

[lunny]

I guess it's a database join or group problem.

[stuzer05]

@stuzer05 which database are you using?

postgres

[edlerd]

I think this is a bug in the LoadIssuesFromBoard function, will submit a PR with a suggestion to fix it.

[stuzer05]

You can verify your fix by duplicating the row in project_issue table like this

Also, I would add a unique constraint for (issue_id, project_id) cols so duplicate rows would never happen in the first place

[edlerd]

You can verify your fix by duplicating the row in project_issue table like this

Is this from your gitea deployment?
Are you using any plugins?

The only place that adds to this table that I found is in project_issues.go where any previous entries to the table are removed before adding a new entry.

Maybe the remove, add comment and create actions from project_issues.go should be done in a transaction?

[lng2020]

Not sure if it's connected with #27746
But it seems more like a front-end issue, like sending the request twice. IIRC, there is an issue about the project board frontend concurrency issue too.