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

Adding repo description with Chi/Jap charaters cause 500 error on ARMv7 platform #2287

New Issue
Closed
opened 2025-11-02 04:31:13 -06:00 by GiteaMirror · 9 comments
GiteaMirror commented 2025-11-02 04:31:13 -06:00
Owner
Copy Link

Originally created by @dragonandy on GitHub (Sep 3, 2018).

  • Gitea version (or commit ref):1.4.2 - 1.5.1 ARMv7
  • Git version:2.7.4
  • Operating system:Ubuntu 16.04 ARM Build
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:
    xorm.log
    gitea.log

Description

MySQL Version 5.7.23-0ubuntu0.16.04.1(Ubuntu) Linux (armv7l)
Adding repo description with Chinese or Japanese charaters cause 500 error on ARMv7 platform
This issue seens to be platform specific only appear on my armv7 board The x86_64 version works just fine with those charaters
I've tested it on gitea 1.4.2 through 1.5.1 with my armv7 board and it all behave the same with a 500 error
The log shows its likely to be a MySQL roll back problem
I try manually change the MySQL database charset/collation to utf8-default and utf8mb4 and still get the 500 error when i try with those char in the description

Screenshots

thanks1 thanks2
Originally created by @dragonandy on GitHub (Sep 3, 2018). <!-- 1. Please speak English, this is the language all of us can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/NsatcWJ) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref):1.4.2 - 1.5.1 ARMv7 - Git version:2.7.4 - Operating system:Ubuntu 16.04 ARM Build - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No - [ ] Not relevant - Log gist: [xorm.log](https://gist.github.com/dragonandy/7867cf9d5a3dd9fb169a08e96b167298) [gitea.log](https://gist.github.com/dragonandy/725bd87cf69635656b97e23e1963e793) ## Description MySQL Version 5.7.23-0ubuntu0.16.04.1(Ubuntu) Linux (armv7l) Adding repo description with Chinese or Japanese charaters cause 500 error on ARMv7 platform This issue seens to be platform specific only appear on my armv7 board The x86_64 version works just fine with those charaters I've tested it on gitea 1.4.2 through 1.5.1 with my armv7 board and it all behave the same with a 500 error The log shows its likely to be a MySQL roll back problem I try manually change the MySQL database charset/collation to utf8-default and utf8mb4 and still get the 500 error when i try with those char in the description ## Screenshots <img width="1157" alt="thanks1" src="https://user-images.githubusercontent.com/4011375/44970976-7f3d4380-af86-11e8-88a6-d06b2ed5d4a0.png"> <img width="1135" alt="thanks2" src="https://user-images.githubusercontent.com/4011375/44971002-9419d700-af86-11e8-93be-e43055c27936.png"> <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/questionissue/stale labels 2025-11-02 04:31:13 -06:00
GiteaMirror commented 2025-11-02 04:31:14 -06:00
Author
Owner
Copy Link

@joeyworld commented on GitHub (Sep 5, 2018):

+1 here. Same issue happens also with Korean characters.

@joeyworld commented on GitHub (Sep 5, 2018): +1 here. Same issue happens also with Korean characters.
GiteaMirror commented 2025-11-02 04:31:15 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Sep 5, 2018):

We need some arm devices to investigate it. Maybe a arm server? @tboerger

@lunny commented on GitHub (Sep 5, 2018): We need some arm devices to investigate it. Maybe a arm server? @tboerger
GiteaMirror commented 2025-11-02 04:31:15 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Sep 5, 2018):

Maybe a arm server? @tboerger

Just rent a Scaleway machine.

@tboerger commented on GitHub (Sep 5, 2018): > Maybe a arm server? @tboerger Just rent a Scaleway machine.
GiteaMirror commented 2025-11-02 04:31:15 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (Sep 12, 2018):

Could be sqlite3 problem?

@lafriks commented on GitHub (Sep 12, 2018): Could be sqlite3 problem?
GiteaMirror commented 2025-11-02 04:31:15 -06:00
Author
Owner
Copy Link

@dragonandy commented on GitHub (Oct 13, 2018):

Could be sqlite3 problem?

probably not
I use a mysql database

@dragonandy commented on GitHub (Oct 13, 2018): > Could be sqlite3 problem? probably not I use a mysql database
GiteaMirror commented 2025-11-02 04:31:16 -06:00
Author
Owner
Copy Link

@dragonandy commented on GitHub (Oct 13, 2018):

I figure out that I can get around with this weird issue by using a database dumped from the database created by gitea x64 version and import it into my ARM device

Here is what I have done

  1. I wrote some Chi/Jap characters in the repo descriptions in my x64 version of gitea for example 你好
  2. use ./gitea dump to dump the gitea data from the x64 side
  3. use mysqlworkbench import the .sql file into my ARM board with the same schema name I use for gitea then grant the same privileges etc. make sure they both have the same settings
  4. I found that the default charset I imported into the ARM side of mysql is Latin so I change it into utf8_general_ci
  5. restart nginx gitea mysqlserver and I can see Chinese charcters appear in the project description and I can modify them without causing a 500 error

To be clear that I use Ubuntu 16.04 on both x64 and ARM side of system
Still doubt that this is a character set problem

@dragonandy commented on GitHub (Oct 13, 2018): I figure out that I can get around with this weird issue by using a database dumped from the database created by gitea x64 version and import it into my ARM device Here is what I have done 1. I wrote some Chi/Jap characters in the repo descriptions in my x64 version of gitea for example `你好` 2. use `./gitea dump` to dump the gitea data from the x64 side 3. use mysqlworkbench import the .sql file into my ARM board with the same schema name I use for gitea then grant the same privileges etc. make sure they both have the same settings 4. I found that the default charset I imported into the ARM side of mysql is Latin so I change it into utf8_general_ci 5. restart nginx gitea mysqlserver and I can see Chinese charcters appear in the project description and I can modify them without causing a 500 error To be clear that I use Ubuntu 16.04 on both x64 and ARM side of system Still doubt that this is a character set problem
GiteaMirror commented 2025-11-02 04:31:16 -06:00
Author
Owner
Copy Link

@tboerger commented on GitHub (Oct 13, 2018):

Are you sure you created the database with utf8 on the arm host?

@tboerger commented on GitHub (Oct 13, 2018): Are you sure you created the database with utf8 on the arm host?
GiteaMirror commented 2025-11-02 04:31:17 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Jan 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 04:31:17 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Jan 6, 2019):

Closing. If this problem still persists please feel free to re-open.

@techknowlogick commented on GitHub (Jan 6, 2019): Closing. If this problem still persists please feel free to re-open.
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/stale type/question
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#2287
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?