github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-21 03:14:01 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Gitea shows outdated commit status with distributed DB backend (eg. TiDB) #12729

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

Originally created by @stevapple on GitHub (Mar 25, 2024).

Description

Gitea doesn’t always show the latest commit status (i.e. being outdated) if you use some distributed database as backend. An auto_increment primary key, though being expected to bump at a step of 1 at every INSERT, may be designed to bump independently on each nodes.

We should update commit_status.go to use the (max(`index`), repo_id, sha) triple to determine the latest commit status, instead of relying on max(id).

Gitea Version

1.21.9

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I’m running Gitea on a Kubernetes cluster, which also hosts Woodpecker CI v2.3.0 and TiDB v7.5.1. Gitea uses TiDB (through mysql) as backend and Woodpecker uses Gitea as forge.

The problem was originally identified as “randomly dropping commit status on either Woodpecker, Gitea and TiDB side”, but after digging into the database it turns out that all commit statuses were there.

Database

MySQL/MariaDB

Originally created by @stevapple on GitHub (Mar 25, 2024). ### Description Gitea doesn’t always show the latest commit status (i.e. being outdated) if you use some distributed database as backend. An `auto_increment` primary key, though being expected to bump at a step of 1 at every `INSERT`, may be designed to bump independently on each nodes. We should update `commit_status.go` to use the ``(max(`index`), repo_id, sha)`` triple to determine the latest commit status, instead of relying on `max(id)`. ### Gitea Version 1.21.9 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I’m running Gitea on a Kubernetes cluster, which also hosts Woodpecker CI v2.3.0 and TiDB v7.5.1. Gitea uses TiDB (through `mysql`) as backend and Woodpecker uses Gitea as forge. The problem was originally identified as “randomly dropping commit status on either Woodpecker, Gitea and TiDB side”, but after digging into the database it turns out that all commit statuses were there. ### Database MySQL/MariaDB
GiteaMirror added the type/bug label 2025-11-02 10:19:19 -06:00
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 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#12729
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?