-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Repositories with (big?) editorconfig can't load #29402
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
Hmm… according to the logs, my primary suspicion is #29310. |
It's SLES 15, run with the amd64 ELF binary, no docker. Might it be hanging because it's waiting for more Output that has been discarded? |
Thanks @MarkusAmshove i am experiencing something similar; for me the page just never finishes (or maybe i have just never been patient enough to wait for more than a couple of minutes). Platform is amd64 binary, no reverse proxy |
same for me on repository home page: gitea version v1.21.6
|
Same problem. editorconfig is 144 lines and 6.8kB if it is relevant. |
Please use Gitea 1.21 nightly, it should have been fixed there. |
Fixed by #29370 and will be released on v1.21.7 |
This is an emergency release to fix the bug #29402. --------- Co-authored-by: wxiaoguang <[email protected]>
Description
Since the update to 1.21.6 I can't view some "home" pages of repositories, resulting in the following logs:
I've cloned one repository that doesn't work in our instance to try.gitea, but there it works fine:
https://try.gitea.io/MarkusAmshove/natls
If I open
/org/repo/pulls
in the browser I instantly get the pulls site. I can even go into pull requests, but once I click on theFiles changed
tab it hangs again.I guess that it has something to do with the editorconfig, since its logged as warning and both the
Files changed
tab and home view of the repository might use it (for the README?).In the example repository on try.gitea you can see that the editorconfig is quite big. Some other repositories that have rather small editorconfigs work fine.
Reverting to 1.21.5 resolved the issue.
Gitea Version
1.21.6
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Downloaded amd64 linux binary, using systemd.
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: