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

Use more friendly error message when a repository can not be accessed #8331

New Issue
Closed
opened 2025-11-02 08:02:35 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 08:02:35 -06:00
Owner
Copy Link

Originally created by @wxiaoguang on GitHub (Jan 10, 2022).

Now, if users access an invalid repository (non-existing, renamed, etc), they would see:

$ git fetch
Gitea: Internal Server Error
Gitea: Internal Server Error
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

The Internal Server Error is quite misleading and there is a error level message in Gitea log:

...ters/private/serv.go:114:ServCommand() [E] Unable to get repository owner: org-name/repo-name Error: user does not exist [uid: 0, name: org-name, keyid: 0]

Since such case is not an serious error, users should not see the Internal Server Error or the error level log messages.

Originally created by @wxiaoguang on GitHub (Jan 10, 2022). Now, if users access an invalid repository (non-existing, renamed, etc), they would see: ``` $ git fetch Gitea: Internal Server Error Gitea: Internal Server Error fatal: Could not read from remote repository. Please make sure you have the correct access rights and the repository exists. ``` The `Internal Server Error` is quite misleading and there is a error level message in Gitea log: ``` ...ters/private/serv.go:114:ServCommand() [E] Unable to get repository owner: org-name/repo-name Error: user does not exist [uid: 0, name: org-name, keyid: 0] ``` Since such case is not an serious error, users should not see the `Internal Server Error` or the error level log messages.
GiteaMirror added the type/enhancement label 2025-11-02 08:02:35 -06:00
GiteaMirror commented 2025-11-02 08:02:36 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 10, 2022):

We should say the repository is not exist or you have no access to this repository.

@lunny commented on GitHub (Jan 10, 2022): We should say the repository is not exist or you have no access to this repository.
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/enhancement
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#8331
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?