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

Empty repository show error 500 #8548

New Issue
Closed
opened 2025-11-02 08:10:28 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2025-11-02 08:10:28 -06:00
Owner
Copy Link

Originally created by @TOMeeeek on GitHub (Feb 11, 2022).

Gitea Version

1.16.1

Git Version

2.13.6

Operating System

Ubuntu server 20.04

How are you running Gitea?

Installed from binary

Database

MySQL

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

https://gist.github.com/TOMeeeek/554a4d6ed4a6336683904887c086f0e4

2022/02/11 12:53:54 ...ers/web/repo/view.go:860:renderCode() [E] GitRepo.IsEmpty: check empty: exit status 129 - usage: git rev-list [OPTION] <commit-id>... [ -->
          limiting output:
            --max-count=<n>
            --max-age=<epoch>
            --min-age=<epoch>
            --sparse
            --no-merges
            --min-parents=<n>
            --no-min-parents
            --max-parents=<n>
            --no-max-parents
            --remove-empty
            --all
            --branches
            --tags
            --remotes
            --stdin
            --quiet
          ordering output:
            --topo-order
            --date-order
            --reverse
          formatting output:
            --parents
            --children
            --objects | --objects-edge
            --unpacked
            --header | --pretty
            --abbrev=<n> | --no-abbrev
            --abbrev-commit
            --left-right
            --count
          special purpose:
            --bisect
            --bisect-vars
            --bisect-all

Description

After upgrading from Gitea 1.15.9 to 1.16.1, a 500 error is reported when entering an empty repository. When downgrading to 1.15.9 again everything is without problems.

Screenshots

No response

Originally created by @TOMeeeek on GitHub (Feb 11, 2022). ### Gitea Version 1.16.1 ### Git Version 2.13.6 ### Operating System Ubuntu server 20.04 ### How are you running Gitea? Installed from binary ### Database MySQL ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist https://gist.github.com/TOMeeeek/554a4d6ed4a6336683904887c086f0e4 ``` 2022/02/11 12:53:54 ...ers/web/repo/view.go:860:renderCode() [E] GitRepo.IsEmpty: check empty: exit status 129 - usage: git rev-list [OPTION] <commit-id>... [ --> limiting output: --max-count=<n> --max-age=<epoch> --min-age=<epoch> --sparse --no-merges --min-parents=<n> --no-min-parents --max-parents=<n> --no-max-parents --remove-empty --all --branches --tags --remotes --stdin --quiet ordering output: --topo-order --date-order --reverse formatting output: --parents --children --objects | --objects-edge --unpacked --header | --pretty --abbrev=<n> | --no-abbrev --abbrev-commit --left-right --count special purpose: --bisect --bisect-vars --bisect-all ``` ### Description After upgrading from Gitea 1.15.9 to 1.16.1, a 500 error is reported when entering an empty repository. When downgrading to 1.15.9 again everything is without problems. ### Screenshots _No response_
GiteaMirror added the issue/confirmedissue/regressiontype/bug labels 2025-11-02 08:10:28 -06:00
GiteaMirror commented 2025-11-02 08:10:29 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 11, 2022):

Possible related to:

I guess that old git need at lease one <commit> in the arguments. New git can omit the <commit>
(update: actually, it's a git bug, old version only, rev-list --all doesn't work on an empty repo)

@wxiaoguang commented on GitHub (Feb 11, 2022): Possible related to: * #18422 ~~I guess that old git need at lease one `<commit>` in the arguments. New git can omit the `<commit>`~~ (update: actually, it's a git bug, old version only, `rev-list --all` doesn't work on an empty repo)
GiteaMirror commented 2025-11-02 08:10:29 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 11, 2022):

Confirmed, it is the case. But git document never mentioned that.

If we run git rev-list --all on an empty git, old git would report errors.

@wxiaoguang commented on GitHub (Feb 11, 2022): Confirmed, it is the case. But git document never mentioned that. If we run `git rev-list --all` on an empty git, old git would report errors.
GiteaMirror commented 2025-11-02 08:10:29 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 11, 2022):

Confirmed, it is the case. But git document never mentioned that.

If we run git rev-list --all on an empty git, old git would report errors.

What's the old git version?

@lunny commented on GitHub (Feb 11, 2022): > Confirmed, it is the case. But git document never mentioned that. > > If we run `git rev-list --all` on an empty git, old git would report errors. What's the old git version?
GiteaMirror commented 2025-11-02 08:10:29 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Feb 12, 2022):

Can we use:

git show-ref HEAD

Instead.

Btw @lunny I missed your reply on my comment:

git rev-list --all

Still just uses the HEAD branch. If we wanted to check if a repo had any branches or tags we'd need to use for-each-ref or the like.

@zeripath commented on GitHub (Feb 12, 2022): Can we use: ``` git show-ref HEAD ``` Instead. Btw @lunny I missed your reply on my comment: ``` git rev-list --all ``` Still just uses the HEAD branch. If we wanted to check if a repo had any branches or tags we'd need to use for-each-ref or the like.
GiteaMirror commented 2025-11-02 08:10:30 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Feb 13, 2022):

What's the old git version?

Author reported 2.13.6, I tried 2.11.x, they all have this bug. It seems that 2.3x doesn't have the bug, but I do not know which version fixed it.

@wxiaoguang commented on GitHub (Feb 13, 2022): > What's the old git version? Author reported `2.13.6`, I tried `2.11.x`, they all have this bug. It seems that `2.3x` doesn't have the bug, but I do not know which version fixed it.
GiteaMirror commented 2025-11-02 08:10:30 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 13, 2022):

git show-ref HEAD

git show-ref HEAD is not work from me.

@lunny commented on GitHub (Feb 13, 2022): > git show-ref HEAD `git show-ref HEAD` is not work from me.
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/confirmed issue/regression 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#8548
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?