-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot import large GPG key #22896
Comments
We won't be able to backport this I'm afraid as there are quite a few migrations in 1.19 that are not in 1.18. I think if you just run |
Thanks @zeripath |
I guess it's worth just double checking that |
Unfortunately go-gitea#20896 does not completely prevent Data too long issues and GPGImportKey needs to be increased too. Fix go-gitea#22896 Signed-off-by: Andrew Thornton <[email protected]>
The test case is detailed in the linked bug report, with a link to a public gpg key grater than 64kb. If your suggestion is implemented in Codeberg and works, I will report back here. |
Unfortunately I don't think that test case would be suitable to add to our test cases - as we'd probably need to add that person's email address in to our testcases! I guess what we need is to create a big keyring for one our test users e.g. |
Sorry, I misunderstood your request at first. |
Unfortunately #20896 does not completely prevent Data too long issues and GPGKeyImport needs to be increased too. Fix #22896 Signed-off-by: Andrew Thornton <[email protected]>
Description
Hello,
This bug has been reported in @Codeberg-org and @forgejo here.
The problem is related with #20894.
The error log involved is
The table
gpg_key_import
should also be migrated to enlarge itscontent
field size.Gitea Version
Codeberg
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?
Forgejo latest build https://codeberg.org/forgejo/forgejo/commits/branch/v1.18/forgejo
Database
MySQL
The text was updated successfully, but these errors were encountered: