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

MySQL/MariaDB: Unique Constraint on Branches doesn't respect casing: UQE_branch_s #12050

New Issue
Closed
opened 2025-11-02 09:56:11 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 09:56:11 -06:00
Owner
Copy Link

Originally created by @sebastian-sauer on GitHub (Nov 20, 2023).

Description

In a repo with two branches feature/test_case and feature\Test_Case gitea throws a 500 exception when syncing branches as the unique constraint is violated.

SyncRepoBranches: Error 1062 (23000): Duplicate entry '<redacted_branch_name>' for key 'UQE_branch_s'

This error happened after an upgrade to 1.21.0 on an existing repo.

Workaround is to rename one of the branches.

Typically having this type of different branch names only based on casing is not needed (imho it's a bug ;) ) - but we shouldn't have a 500 page when accessing the repo.

Gitea Version

1.21.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Linux

How are you running Gitea?

Official binary

Database

MySQL/MariaDB

Originally created by @sebastian-sauer on GitHub (Nov 20, 2023). ### Description In a repo with two branches `feature/test_case` and `feature\Test_Case` gitea throws a 500 exception when syncing branches as the unique constraint is violated. `SyncRepoBranches: Error 1062 (23000): Duplicate entry '<redacted_branch_name>' for key 'UQE_branch_s'` This error happened after an upgrade to 1.21.0 on an existing repo. Workaround is to rename one of the branches. Typically having this type of different branch names only based on casing is not needed (imho it's a bug ;) ) - but we shouldn't have a 500 page when accessing the repo. ### Gitea Version 1.21.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System Linux ### How are you running Gitea? Official binary ### Database MySQL/MariaDB
GiteaMirror added the type/bugissue/workaround labels 2025-11-02 09:56:11 -06:00
GiteaMirror commented 2025-11-02 09:56:12 -06:00
Author
Owner
Copy Link

@yorliuk commented on GitHub (Nov 20, 2023):

I got the same error in Gitea log after updating to 1.21.
...dules/context/api.go:105:ServerError() [E] SyncRepoBranches: Error 1062 (23000): Duplicate entry '<BRANCH_NAME>' for key 'branch.UQE_branch_s'

But I can't find such branch in DB.
mysql Ver 8.0.28 for Linux on x86_64 (MySQL Community Server - GPL)

@yorliuk commented on GitHub (Nov 20, 2023): I got the same error in Gitea log after updating to 1.21. `...dules/context/api.go:105:ServerError() [E] SyncRepoBranches: Error 1062 (23000): Duplicate entry '<BRANCH_NAME>' for key 'branch.UQE_branch_s'` But I can't find such branch in DB. `mysql Ver 8.0.28 for Linux on x86_64 (MySQL Community Server - GPL)`
GiteaMirror commented 2025-11-02 09:56:12 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Nov 20, 2023):

Related: https://github.com/go-gitea/gitea/issues/25909

@silverwind commented on GitHub (Nov 20, 2023): Related: https://github.com/go-gitea/gitea/issues/25909
GiteaMirror commented 2025-11-02 09:56:12 -06:00
Author
Owner
Copy Link

@sebastian-sauer commented on GitHub (Nov 20, 2023):

Are we "allowed" to remove a unique constraint in a patch release?

@sebastian-sauer commented on GitHub (Nov 20, 2023): Are we "allowed" to remove a unique constraint in a patch release?
GiteaMirror commented 2025-11-02 09:56:13 -06:00
Author
Owner
Copy Link

@yorliuk commented on GitHub (Nov 20, 2023):

I got the same error in Gitea log after updating to 1.21. ...dules/context/api.go:105:ServerError() [E] SyncRepoBranches: Error 1062 (23000): Duplicate entry '<BRANCH_NAME>' for key 'branch.UQE_branch_s'

But I can't find such branch in DB. mysql Ver 8.0.28 for Linux on x86_64 (MySQL Community Server - GPL)

It helped: https://github.com/go-gitea/gitea/issues/25909#issuecomment-1637254581

@yorliuk commented on GitHub (Nov 20, 2023): > I got the same error in Gitea log after updating to 1.21. `...dules/context/api.go:105:ServerError() [E] SyncRepoBranches: Error 1062 (23000): Duplicate entry '<BRANCH_NAME>' for key 'branch.UQE_branch_s'` > > But I can't find such branch in DB. `mysql Ver 8.0.28 for Linux on x86_64 (MySQL Community Server - GPL)` It helped: https://github.com/go-gitea/gitea/issues/25909#issuecomment-1637254581
GiteaMirror commented 2025-11-02 09:56:13 -06:00
Author
Owner
Copy Link

@silverwind commented on GitHub (Nov 20, 2023):

Are we "allowed" to remove a unique constraint in a patch release?

Anything reasonable is possible, but I think the solution is to make the field case-sensitive.

@silverwind commented on GitHub (Nov 20, 2023): > Are we "allowed" to remove a unique constraint in a patch release? Anything reasonable is possible, but I think the solution is to make the field case-sensitive.
GiteaMirror commented 2025-11-02 09:56:13 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 29, 2023):

For 1.21 (unlucky...) users, the workaround is to run the SQL manually:

ALTER TABLE branch MODIFY COLUMN `name` VARCHAR(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL

It won't cause side-effect and won't conflict with the complete fix (if there is anything wrong, it could be revert to old COLLATE utf8mb4_general_ci)

@wxiaoguang commented on GitHub (Dec 29, 2023): For 1.21 (unlucky...) users, the workaround is to run the SQL manually: ``` ALTER TABLE branch MODIFY COLUMN `name` VARCHAR(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin NOT NULL ``` It won't cause side-effect and won't conflict with the complete fix (if there is anything wrong, it could be revert to old `COLLATE utf8mb4_general_ci`)
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/workaround 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#12050
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?