-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Broken repo - don't understand why and how to fix #34424
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
not sure if relevant but i saw this in the logs before the repository broke (3 times in a row the same failure of the snippet below)
|
Any way to reproduce this issue locally? |
Can you visit the directory of that repository from server side. |
unfortunately, i don't know what triggers this |
Yeah I can, in the issue description I do that:
|
fsck also doesn't detect anything wrong:
|
Is there any branches in this repository except tags? |
yes,
|
Does the commit |
yes,
I don't see any issues with permissions, ran ran in broken repo (inside the gitea container):
|
there doesn't seem to be any issue with the git repo itself as i can do git clone, push commits, etc... |
this seems to be the case, i queried the "repository" table in the postgres db and the field "status" has the value 3, which all the other repos have status 0 |
ok so forcing status=0 seems to have recovered my repo for now |
The scenario is rare but I sent a PR #34443 to make it can be recovered automatically. |
Thanks both! |
Backport #34444 by wxiaoguang Fix #34424 Co-authored-by: wxiaoguang <[email protected]>
Description
"The Git data underlying this repository cannot be read. Contact the administrator of this instance or delete this repository."
Have this happen to two repos so far on the last few months. Solved first by deleting the repo and re-pushing the code, but really would be better if this doesn't happen
I can still pull/push to the repo from git tools, but anything involving gitea UI or actions is completely broken on these repos.
(Note: the actual repo name has been replaced with in the snippets below)
The repo seems fine:
I have this in the app.ini:
I don't really get anything interesting in the logs when trying to access the repo via gitea (a bit more shown in the gist but probably not useful):
Funnily enough, I am able to clone the repo with no issues (sorry for some PT language):
Pushing new commits / pulling etc also works.
Gitea Version
1.23.7
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
https://gist.github.com/davidfrickert/753cd38cfc1462f92b1863f3b8241c24
Screenshots
Git Version
git --version -> git version 2.47.2
Operating System
Fedora 41 Server
How are you running Gitea?
Helm chart on Kubernetes (3 gitea instances, 3 redis instances)
Using the official docker image from gitea v1.23.7
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: