github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-15 20:09:18 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Wrong pull request count in a single repo #2953

New Issue
Closed
opened 2025-11-02 04:55:10 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 04:55:10 -06:00
Owner
Copy Link

Originally created by @xoxys on GitHub (Feb 21, 2019).

  • Gitea version (or commit ref): 1.7.2
  • Git version:
  • Operating system: CentOS 7
  • 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 have a single repository which displays a wrong PR count. If no PR is opened, it displays -1, if one PR is opened it displays 0 and so on. All other repos work fine. If this is not a bug, how to fix this by hand?

Screenshots

image

image

Originally created by @xoxys on GitHub (Feb 21, 2019). - Gitea version (or commit ref): 1.7.2 - Git version: - Operating system: CentOS 7 - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [X] Not relevant - Log gist: ## Description I have a single repository which displays a wrong PR count. If no PR is opened, it displays `-1`, if one PR is opened it displays `0` and so on. All other repos work fine. If this is not a bug, how to fix this by hand? ## Screenshots ![image](https://user-images.githubusercontent.com/3391958/53157449-d3ce8c80-35c1-11e9-9a04-d33956b6fb27.png) ![image](https://user-images.githubusercontent.com/3391958/53158459-ea75e300-35c3-11e9-870c-6bebe4175d0e.png)
GiteaMirror added the issue/staletype/bug labels 2025-11-02 04:55:10 -06:00
GiteaMirror commented 2025-11-02 04:55:11 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Apr 22, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 22, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:55:11 -06:00
Author
Owner
Copy Link

@xoxys commented on GitHub (Apr 22, 2019):

Not solved

@xoxys commented on GitHub (Apr 22, 2019): Not solved
GiteaMirror commented 2025-11-02 04:55:11 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Apr 22, 2019):

update pr count in repositories table in sql

@lafriks commented on GitHub (Apr 22, 2019): update pr count in repositories table in sql
GiteaMirror commented 2025-11-02 04:55:11 -06:00
Author
Owner
Copy Link

@xoxys commented on GitHub (Apr 22, 2019):

@lafriks: I'll give it a try

@xoxys commented on GitHub (Apr 22, 2019): @lafriks: I'll give it a try
GiteaMirror commented 2025-11-02 04:55:11 -06:00
Author
Owner
Copy Link

@richmahn commented on GitHub (May 30, 2019):

I had this happen with a user today. The URL is https://git.door43.org/unfoldingWord/en_ugg/pulls/95 showing a -1 for open Pull Requests, and this issue is the culprit, where it somehow closed twice. From the user:

I received an error message (500?) when I merged a change. It did not bringing up the merged successful page and the "Do you want to delete the branch" choice.
That said, it did merge the change I was making. I then went in and manually deleted the branch I merged into master. But there appears to be a problem with the merge procedure. I also note that there is a negative 1 pull request. This may also be part of the problem.

From the gitea.log:

2019/05/30 13:49:49 [...routers/repo/pull.go:943 CompareAndPullRequestPost()] [E] NewPullRequest: newIssue: Error 1062: Duplicate entry '28434-95' for key 'UQE_issue_repo_index'

Maybe tries to insert rather than update?

@richmahn commented on GitHub (May 30, 2019): I had this happen with a user today. The URL is https://git.door43.org/unfoldingWord/en_ugg/pulls/95 showing a `-1` for open Pull Requests, and this issue is the culprit, where it somehow closed twice. From the user: > I received an error message (500?) when I merged a change. It did not bringing up the merged successful page and the "Do you want to delete the branch" choice. > That said, it did merge the change I was making. I then went in and manually deleted the branch I merged into master. But there appears to be a problem with the merge procedure. I also note that there is a negative 1 pull request. This may also be part of the problem. From the gitea.log: > 2019/05/30 13:49:49 [...routers/repo/pull.go:943 CompareAndPullRequestPost()] [E] NewPullRequest: newIssue: Error 1062: Duplicate entry '28434-95' for key 'UQE_issue_repo_index' Maybe tries to insert rather than update?
GiteaMirror commented 2025-11-02 04:55:12 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 31, 2019):

@richmahn you issue should have been fixed by my PR https://github.com/go-gitea/gitea/pull/6973 , but it's not back ported to v1.8

@xoxys I think this maybe caused by merging some pull request failed and panic.

@lunny commented on GitHub (May 31, 2019): @richmahn you issue should have been fixed by my PR https://github.com/go-gitea/gitea/pull/6973 , but it's not back ported to v1.8 @xoxys I think this maybe caused by merging some pull request failed and panic.
GiteaMirror commented 2025-11-02 04:55:12 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jul 30, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jul 30, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:55:12 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jul 30, 2019):

Linked PR is merged, closing this ticket.

Please re-open if needed (after updating to latest Gitea)

@techknowlogick commented on GitHub (Jul 30, 2019): Linked PR is merged, closing this ticket. Please re-open if needed (after updating to latest Gitea)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/stale type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2953
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?