mirror of
https://github.com/go-gitea/gitea.git
synced 2026-03-12 10:39:38 -05:00
Internal Server Error 500 when browsing the front page of a particular repository #835
Closed
opened 2025-11-02 03:38:12 -06:00 by GiteaMirror
·
14 comments
No Branch/Tag Specified
main
release/v1.25
release/v1.24
release/v1.23
release/v1.22
release/v1.21
release/v1.20
release/v1.19
release/v1.18
release/v1.17
release/v1.16
release/v1.15
release/v1.14
release/v1.13
release/v1.12
release/v1.11
release/v1.10
release/v1.9
release/v1.8
v1.25.3
v1.25.2
v1.25.1
v1.25.0
v1.24.7
v1.25.0-rc0
v1.26.0-dev
v1.24.6
v1.24.5
v1.24.4
v1.24.3
v1.24.2
v1.24.1
v1.24.0
v1.23.8
v1.24.0-rc0
v1.25.0-dev
v1.23.7
v1.23.6
v1.23.5
v1.23.4
v1.23.3
v1.23.2
v1.23.1
v1.23.0
v1.23.0-rc0
v1.24.0-dev
v1.22.6
v1.22.5
v1.22.4
v1.22.3
v1.22.2
v1.22.1
v1.22.0
v1.23.0-dev
v1.22.0-rc1
v1.21.11
v1.22.0-rc0
v1.21.10
v1.21.9
v1.21.8
v1.21.7
v1.21.6
v1.21.5
v1.21.4
v1.21.3
v1.21.2
v1.20.6
v1.21.1
v1.21.0
v1.21.0-rc2
v1.21.0-rc1
v1.20.5
v1.22.0-dev
v1.21.0-rc0
v1.20.4
v1.20.3
v1.20.2
v1.20.1
v1.20.0
v1.19.4
v1.21.0-dev
v1.20.0-rc2
v1.20.0-rc1
v1.20.0-rc0
v1.19.3
v1.19.2
v1.19.1
v1.19.0
v1.19.0-rc1
v1.20.0-dev
v1.19.0-rc0
v1.18.5
v1.18.4
v1.18.3
v1.18.2
v1.18.1
v1.18.0
v1.17.4
v1.18.0-rc1
v1.19.0-dev
v1.18.0-rc0
v1.17.3
v1.17.2
v1.17.1
v1.17.0
v1.17.0-rc2
v1.16.9
v1.17.0-rc1
v1.18.0-dev
v1.16.8
v1.16.7
v1.16.6
v1.16.5
v1.16.4
v1.16.3
v1.16.2
v1.16.1
v1.16.0
v1.15.11
v1.17.0-dev
v1.16.0-rc1
v1.15.10
v1.15.9
v1.15.8
v1.15.7
v1.15.6
v1.15.5
v1.15.4
v1.15.3
v1.15.2
v1.15.1
v1.14.7
v1.15.0
v1.15.0-rc3
v1.14.6
v1.15.0-rc2
v1.14.5
v1.16.0-dev
v1.15.0-rc1
v1.14.4
v1.14.3
v1.14.2
v1.14.1
v1.14.0
v1.13.7
v1.14.0-rc2
v1.13.6
v1.13.5
v1.14.0-rc1
v1.15.0-dev
v1.13.4
v1.13.3
v1.13.2
v1.13.1
v1.13.0
v1.12.6
v1.13.0-rc2
v1.14.0-dev
v1.13.0-rc1
v1.12.5
v1.12.4
v1.12.3
v1.12.2
v1.12.1
v1.11.8
v1.12.0
v1.11.7
v1.12.0-rc2
v1.11.6
v1.12.0-rc1
v1.13.0-dev
v1.11.5
v1.11.4
v1.11.3
v1.10.6
v1.12.0-dev
v1.11.2
v1.10.5
v1.11.1
v1.10.4
v1.11.0
v1.11.0-rc2
v1.10.3
v1.11.0-rc1
v1.10.2
v1.10.1
v1.10.0
v1.9.6
v1.9.5
v1.10.0-rc2
v1.11.0-dev
v1.10.0-rc1
v1.9.4
v1.9.3
v1.9.2
v1.9.1
v1.9.0
v1.9.0-rc2
v1.10.0-dev
v1.9.0-rc1
v1.8.3
v1.8.2
v1.8.1
v1.8.0
v1.8.0-rc3
v1.7.6
v1.8.0-rc2
v1.7.5
v1.8.0-rc1
v1.9.0-dev
v1.7.4
v1.7.3
v1.7.2
v1.7.1
v1.7.0
v1.7.0-rc3
v1.6.4
v1.7.0-rc2
v1.6.3
v1.7.0-rc1
v1.7.0-dev
v1.6.2
v1.6.1
v1.6.0
v1.6.0-rc2
v1.5.3
v1.6.0-rc1
v1.6.0-dev
v1.5.2
v1.5.1
v1.5.0
v1.5.0-rc2
v1.5.0-rc1
v1.5.0-dev
v1.4.3
v1.4.2
v1.4.1
v1.4.0
v1.4.0-rc3
v1.4.0-rc2
v1.3.3
v1.4.0-rc1
v1.3.2
v1.3.1
v1.3.0
v1.3.0-rc2
v1.3.0-rc1
v1.2.3
v1.2.2
v1.2.1
v1.2.0
v1.2.0-rc3
v1.2.0-rc2
v1.1.4
v1.2.0-rc1
v1.1.3
v1.1.2
v1.1.1
v1.1.0
v1.0.2
v1.0.1
v1.0.0
v0.9.99
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
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
Mirrored from GitHub Pull Request
No Label
type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/gitea#835
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
Originally created by @typeless on GitHub (Jun 22, 2017).
Gitea version (or commit ref):
Gitea Version: 1.1.0+351-g7051e60
Git version:
2.7.4
Operating system:
Ubuntu 16.04 64bit
Database (use
[x]):Can you reproduce the bug at https://try.gitea.io:
Log gist:
Description
Looks like the added '^' in
474d636794 (diff-c689e587c4a9ef800a342d225b8ff732R271)will cause the problem.The following is the git command that causes the error
Note that the commit in question is the initial commit of the repository.
@typeless commented on GitHub (Jun 22, 2017):
Removing the trailing '^' seems to fix the problem. I haven't figured out the root cause though.
@ethantkoenig commented on GitHub (Jun 22, 2017):
@typeless I believe this will be fixed by https://github.com/go-gitea/git/pull/66. Can you pull the latest changes from code.gitea.io/git, and see if that fixes the problem?
@typeless commented on GitHub (Jun 23, 2017):
@ethantkoenig You are correct. The problem is fixed. 👍
@typeless commented on GitHub (Jun 23, 2017):
Sorry but this problem is probably not fixed yet.
Currently I made a workaround which might be the correct fix or not:
@lunny commented on GitHub (Jun 23, 2017):
@typeless could you send a PR?
@typeless commented on GitHub (Jun 23, 2017):
@lunny No problem.
@ethantkoenig commented on GitHub (Jun 23, 2017):
@typeless Omitting the caret does not fix the root of the problem (and introduces a potential infinite loop). Could you share the repo where the error still occurs, so that we can diagnose what the underlying cause is?
@typeless commented on GitHub (Jun 23, 2017):
@ethantkoenig I am afraid it's not possible because the repo is very large. The only thing I found suspicious is the file which causes the problem is a
.gitignorewhich happens to have only one commit history. And based on the log I collected, the actual git command which led to the error can make the same error if I try to enter the command via CLI. A file with only one commit is actually not possible to get its parent commit using the caret.@ethantkoenig commented on GitHub (Jun 24, 2017):
@typeless Could you checkout https://github.com/ethantkoenig/gitea/tree/debug_get_commits_info (latest gitea master plus some print statements for debugging), try to view the problematic repo, and show me what gets printed?
@typeless commented on GitHub (Jun 26, 2017):
@ethantkoenig I have to cut the rest the filenames listing otherwise it would exceed the maximum limit of the comment. Those are not interesting though, just list of the paths/filenames. (Actually, the files are too many. The server was hanging so I had to stop it manually.)
@ethantkoenig commented on GitHub (Jun 26, 2017):
@typeless Sorry, this isn't enough to debug the problem. Is the repo you're using publicly hosted somewhere? It would be helpful if I could run the problematic commands on my own machine.
@typeless commented on GitHub (Jun 26, 2017):
@ethantkoenig No, it's not public hosted.
I can try to shrink it or git-filter-branch it if that can preserve the problem.
@ethantkoenig commented on GitHub (Jun 26, 2017):
@typeless Are the repo's contents sensitive?
If the repo's contents are not sensitive, could you upload the repo to try.gitea.io?
If the repo's contents are sensitive, could you share the full log of what I had you run earlier (not here, but maybe in a Github Gist)?
@typeless commented on GitHub (Jun 27, 2017):
@ethantkoenig The repo belongs to the company I work for. So theoretically any publishment requires to go through certain managerial/bureaucratic process to get the legal permission, which I am reluctant to bother with. 😆
The good news (or bad news?) is that the problem can no longer be reproduced now. It's probably due to the changes happening to the repo. So I will close this for now.