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

Cannot Add Large GPG Key #9441

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

Originally created by @lekoOwO on GitHub (Aug 21, 2022).

Description

AddPublicKey: Error 1406: Data too long for column 'content' at row 1 happens when importing a longer GPG Key (e.g. 4096 key size often reaches the 64KB limit in case of MySQL's TEXT field)

Using MySQL 8.

Gitea Version

1.18.3

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?

Using Docker.

Database

MySQL

Originally created by @lekoOwO on GitHub (Aug 21, 2022). ### Description `AddPublicKey: Error 1406: Data too long for column 'content' at row 1` happens when importing a longer GPG Key (e.g. 4096 key size often reaches the 64KB limit in case of MySQL's TEXT field) Using MySQL 8. ### Gitea Version 1.18.3 ### 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? Using Docker. ### Database MySQL
GiteaMirror added the type/bug label 2025-11-02 08:38:58 -06:00
GiteaMirror commented 2025-11-02 08:38:59 -06:00
Author
Owner
Copy Link

@fsologureng commented on GitHub (Feb 13, 2023):

Hello,
This bug should be reopened because importing gpg keys suffered from the same issue.

Reported in @Codeberg-org and @Forgejo here.

The error log involved is

2023/02/12 15:37:27 ...user/setting/keys.go:117:KeysPost() [E] [63e907b5-20] AddPublicKey: Error 1406: Data too long for column 'content' at row 1

The table gpg_key_import should also be migrated to enlarge its content field size.

@fsologureng commented on GitHub (Feb 13, 2023): Hello, This bug should be reopened because importing gpg keys suffered from the same issue. Reported in @Codeberg-org and @Forgejo [here](https://codeberg.org/forgejo/forgejo/issues/359). The error log involved is ~~~ 2023/02/12 15:37:27 ...user/setting/keys.go:117:KeysPost() [E] [63e907b5-20] AddPublicKey: Error 1406: Data too long for column 'content' at row 1 ~~~ The table `gpg_key_import` should also be migrated to enlarge its `content` field size.
GiteaMirror commented 2025-11-02 08:38:59 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 13, 2023):

Instead of commenting on bugs that have been closed for over 6 months it's better to open a new one and reference the old one.

@zeripath commented on GitHub (Feb 13, 2023): Instead of commenting on bugs that have been closed for over 6 months it's better to open a new one and reference the old one.
GiteaMirror commented 2025-11-02 08:39:00 -06:00
Author
Owner
Copy Link

@fsologureng commented on GitHub (Feb 13, 2023):

Ok. No problem.

@fsologureng commented on GitHub (Feb 13, 2023): Ok. No problem.
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#9441
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?