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

uploading rpm with large metadata fails with mysql/mariadb database #14742

New Issue
Closed
opened 2025-11-02 11:21:46 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 11:21:46 -06:00
Owner
Copy Link

Originally created by @alexth4ef9 on GitHub (Jul 10, 2025).

Description

same bug as #29110

log:

2025/07/10 17:22:29 .../packages/packages.go:312:addFileToPackageVersionUnchecked() [I] [SQL] INSERT INTO package_property (ref_type,ref_id,name,value) VALUES (?,?,?,?) [1 4535 rpm.metadata {"architecture":"x86_64","epoch":"0","version":"6.15.4","release":"200.fc42","vendor":"Fedora Project","group":"Unspecified","packager":"Fedora

... 1.7MB json ...

Linux v6.14.0-0.rc0.95ec54a420b8"}]}] - 36.435431ms
2025/07/10 17:22:29 .../packages/packages.go:313:addFileToPackageVersionUnchecked() [E] Error setting package file property: Error 1406 (22001): Data too long for column 'value' at row 1
2025/07/10 17:22:29 .../api/packages/rpm/rpm.go:172:UploadPackageFile() [I] [SQL] ROLLBACK [] - 2.011846ms
2025/07/10 17:22:29 .../api/packages/rpm/rpm.go:29:apiError() [E] Error 1406 (22001): Data too long for column 'value' at row 1
2025/07/10 17:22:29 HTTPRequest [I] router: completed PUT /api/packages/shardborn/rpm/fedora/f42/upload?sign=true for 10.89.0.6:0, 500 Internal Server Error in 413.7ms @ packages/api.go:553(packages.CommonRoutes.func1.(*Router).Group.CommonRoutes.func1.18.65)

according to https://github.com/go-gitea/gitea/blob/main/models/packages/package_property.go#L35 value column is of type TEXT (64kB on MySQL/MariaDB, unlimited on PostgreSQL)

this is similar to #16656

rpm to reproduce fedora 42 kernel-core (dnf download kernel-core)

no problem to upload it on demo.gitea.com (other database)

Gitea Version

1.24.2

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

rootless podman container on fedora coreos 42

How are you running Gitea?

running gitea/gitea:latest-rootless

Database

MySQL/MariaDB

Originally created by @alexth4ef9 on GitHub (Jul 10, 2025). ### Description same bug as #29110 log: 2025/07/10 17:22:29 .../packages/packages.go:312:addFileToPackageVersionUnchecked() [I] [SQL] INSERT INTO `package_property` (`ref_type`,`ref_id`,`name`,`value`) VALUES (?,?,?,?) [1 4535 rpm.metadata {"architecture":"x86_64","epoch":"0","version":"6.15.4","release":"200.fc42","vendor":"Fedora Project","group":"Unspecified","packager":"Fedora ... 1.7MB json ... Linux v6.14.0-0.rc0.95ec54a420b8"}]}] - 36.435431ms 2025/07/10 17:22:29 .../packages/packages.go:313:addFileToPackageVersionUnchecked() [E] Error setting package file property: Error 1406 (22001): Data too long for column 'value' at row 1 2025/07/10 17:22:29 .../api/packages/rpm/rpm.go:172:UploadPackageFile() [I] [SQL] ROLLBACK [] - 2.011846ms 2025/07/10 17:22:29 .../api/packages/rpm/rpm.go:29:apiError() [E] Error 1406 (22001): Data too long for column 'value' at row 1 2025/07/10 17:22:29 HTTPRequest [I] router: completed PUT /api/packages/shardborn/rpm/fedora/f42/upload?sign=true for 10.89.0.6:0, 500 Internal Server Error in 413.7ms @ packages/api.go:553(packages.CommonRoutes.func1.(*Router).Group.CommonRoutes.func1.18.65) according to https://github.com/go-gitea/gitea/blob/main/models/packages/package_property.go#L35 value column is of type TEXT (64kB on MySQL/MariaDB, unlimited on PostgreSQL) this is similar to #16656 rpm to reproduce fedora 42 kernel-core (dnf download kernel-core) no problem to upload it on demo.gitea.com (other database) ### Gitea Version 1.24.2 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System rootless podman container on fedora coreos 42 ### How are you running Gitea? running gitea/gitea:latest-rootless ### Database MySQL/MariaDB
GiteaMirror added the type/bugissue/workaround labels 2025-11-02 11:21:46 -06:00
GiteaMirror commented 2025-11-02 11:21:47 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 11, 2025):

MySQL LONGTEXT problem is still not resolved. @lunny

And also this one:

As a workaround, you can manually alter that column to "LONGTEXT" type.

@wxiaoguang commented on GitHub (Jul 11, 2025): MySQL LONGTEXT problem is still not resolved. @lunny And also this one: * https://github.com/go-gitea/gitea/issues/34764#issuecomment-2986102920 > As a workaround, you can manually alter that column to "LONGTEXT" type.
GiteaMirror commented 2025-11-02 11:21:47 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Jul 17, 2025):

@lunny

@wxiaoguang commented on GitHub (Jul 17, 2025): @lunny
GiteaMirror commented 2025-11-02 11:21:47 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jul 17, 2025):

Image

In MySQL, the TEXT type has a size limit of 64KB. Therefore, I believe we should change the Value column to LONGTEXT to support larger data. This change will require a migration to update the column type accordingly.
For other supported databases, the TEXT type typically allows for larger sizes, but we should still ensure compatibility across all of them.

@lunny commented on GitHub (Jul 17, 2025): <img width="523" height="167" alt="Image" src="https://github.com/user-attachments/assets/98b8b077-90a7-4352-be69-cb2bf089b901" /> In MySQL, the TEXT type has a size limit of 64KB. Therefore, I believe we should change the Value column to LONGTEXT to support larger data. This change will require a migration to update the column type accordingly. For other supported databases, the TEXT type typically allows for larger sizes, but we should still ensure compatibility across all of them.
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#14742
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?