-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Error 500 when accessing branches in repo #29936
Comments
Maybe it could be "fixed" by "Fix loadOneBranch panic #29938" |
Oh one more thing, maybe you could try to click "Sync branches" on the site admin panel, to re-sync all branches. |
@wxiaoguang I clicked on But now I dont get the Error 500!! Woohoo! |
Try to fix #29936 Far from ideal, but still better than panic.
Try to fix go-gitea#29936 Far from ideal, but still better than panic.
Description
Good Day,
Hope I've posted all relevant info.
We have a repo inside an org, which does not allow us to view its branches via the UI. We had several branches that were automatically created with our pipeline via the API. We've been doing this for several months now. Only yesterday we noticed that we could not see the branches in the UI (this was never the case before). We were under version
1.21.7
and were hoping updating to1.21.8
would help, but nothing.Since we could see all the branches via the API, we decided to delete all the branches via API except for
main
. Now onlymain
shows via the API. Interestingly under the UI, it still shows that2 Branches
exists. (see screenshots)When i click on the
tto-device-discovery
branch, i get a404
not found code page, which should be correct (see screenshot)Looking at other tickets, i check permissions on the filesystem, but nothing interesting
Anything I can do to resolve this?
Below are the logs
Screenshots
Gitea Version
1.21.8
Can you reproduce the bug on the Gitea demo site?
No
Operating System
Rocky Linux 9 (gitea inside docker)
Browser Version
Google Chrome Version 120.0.6099.224 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: