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

500 internal server error when renaming an organisation as reserved name #8201

New Issue
Closed
opened 2025-11-02 07:57:13 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 07:57:13 -06:00
Owner
Copy Link

Originally created by @cobber on GitHub (Dec 1, 2021).

Gitea Version

1.15.3

Git Version

No response

Operating System

No response

How are you running Gitea?

standalone binary installation gitea-1.15.3-linux-arm-6 image installed under a dedicated "gitea" user

Database

SQLite

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Description

When I tried to rename one of my organisations to "admin" (for my git repo's with administrative scripts etc) I got a nondescript "500" error (without "internal server error" or any other information).

Being my own gitea admin, I was able to find the log entry:
2021/12/01 21:04:40 ...s/web/org/setting.go:72:SettingsPost() [E] ChangeUserName: name is reserved [name: admin]

It would be much more user friendly if at least this error message was displayed in the UI.

As far as I can tell this is being triggered via CreateOrgnization() when it gets an error from user_model.IsUsableUsername()

Also, the list of reserved names in models/user/user.go (reservedUsernames var) would be useful information to help the user understand what went wrong.

Screenshots

No response

Originally created by @cobber on GitHub (Dec 1, 2021). ### Gitea Version 1.15.3 ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? standalone binary installation gitea-1.15.3-linux-arm-6 image installed under a dedicated "gitea" user ### Database SQLite ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Description When I tried to rename one of my organisations to "admin" (for my git repo's with administrative scripts etc) I got a nondescript "500" error (without "internal server error" or any other information). Being my own gitea admin, I was able to find the log entry: 2021/12/01 21:04:40 ...s/web/org/setting.go:72:SettingsPost() [E] ChangeUserName: name is reserved [name: admin] It would be much more user friendly if at least this error message was displayed in the UI. As far as I can tell this is being triggered via CreateOrgnization() when it gets an error from user_model.IsUsableUsername() Also, the list of reserved names in models/user/user.go (reservedUsernames var) would be useful information to help the user understand what went wrong. ### Screenshots _No response_
GiteaMirror commented 2025-11-02 07:57:15 -06:00
Author
Owner
Copy Link

@a1012112796 commented on GitHub (Dec 2, 2021):

Has you try the new version (v1.15.6) ?

@a1012112796 commented on GitHub (Dec 2, 2021): Has you try the new version (**v1.15.6**) ?
GiteaMirror commented 2025-11-02 07:57:15 -06:00
Author
Owner
Copy Link

@cobber commented on GitHub (Dec 2, 2021):

Yep, 1.15.6 shows the same error, but I see you have added a patch.
I'll check it again when 1.15.7 is released.
Thanks.

@cobber commented on GitHub (Dec 2, 2021): Yep, 1.15.6 shows the same error, but I see you have added a patch. I'll check it again when 1.15.7 is released. Thanks.
GiteaMirror commented 2025-11-02 07:57:16 -06:00
Author
Owner
Copy Link

@cobber commented on GitHub (Jan 20, 2022):

just checked: 1.15.7 no longer crashes, just shows 'illegal_username' in a red dialog box.
Could be prettier, but is definitely a big improvement :-)

@cobber commented on GitHub (Jan 20, 2022): just checked: 1.15.7 no longer crashes, just shows 'illegal_username' in a red dialog box. Could be prettier, but is definitely a big improvement :-)
GiteaMirror commented 2025-11-02 07:57:17 -06:00
Author
Owner
Copy Link

@Gusted commented on GitHub (Jan 20, 2022):

just shows 'illegal_username' in a red dialog box.
Could be prettier, but is definitely a big improvement :-)

#18342

@Gusted commented on GitHub (Jan 20, 2022): > just shows 'illegal_username' in a red dialog box. > Could be prettier, but is definitely a big improvement :-) #18342
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
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#8201
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?