-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Indexer crashes #5324
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
Which version of Git are you using? |
git --version Debian Buster X64 |
I have a similar problem: same error message, same status 128. And Gitea is then taking up 44% of my whole RAM!
to:
on Archlinux, with my Ansible configuration applied to Please ask for details if you need more. |
Same here on RHEL:
|
Same after updating from
|
Same, using 1.6.0, debian 9 64bit, git 2.17.1 2018/11/30 22:56:10 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: git cat-file 9d7337a3b028095abbb0ee3dec460544d019d1f6: bad file |
same, using 1.6.1, rhel 7.5 X86_64bit, git 2.14.1
|
This is still present in 1.7 for me |
The indexer seems to be a bit useless with big repos :( |
As things stand, it is also useless with little repos, because you have to disable it to keep it from eating all your RAM :-/ |
indexing and searching are essential to code related work, any way to improve this in gitea, as far as I can tell, this is the only obvious weak area at the moment. |
@laoshaw Yes, that needs more work. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
Does someone know the current status of this issue? |
@tYYGH If you switch the Repo Indexer off, you will not be able to search for code in Gitea anymore. |
I am wondering about the indexer situation as well. Has there been any improvements? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions. |
@Stale you suck |
Here is a full Drone CI Cloud buildlog running |
is this fixed now? because it looks like it is fixed in 1.9.2 (https://cloud.drone.io/alpinelinux/aports/11110/3/1) |
I will have a look but I remember a PR for a buffered |
@guillep2k Yes, you greatly improve indexer code and others have greatly contribute to git related performances. I will close this issue then. |
* Add aarch64 again - to test it with CI - Delete problem (go-gitea/gitea#5324) from image file * fix make test - Exclude tests
Indexer crashes with the lines below
I am using Gitea Version: 34695f4 on Debian Testing
2018/11/12 11:37:06 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: git cat-file: could not get object info
2018/11/12 11:37:06 [I] Done populating the repo indexer with existing repositories
2018/11/12 11:37:07 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: Not a valid object name 33af0e1f6c425959dd41b96752e61f50949e0118
57c601d489a0901efaa5ded23b724bd5fb7f5af2
2018/11/12 11:37:22 [.../runtime/asm_amd64.s:1333 goexit()] [E] updateRepoIndexer: exit status 128 - fatal: Not a valid object name d23a53c74af7601d45f90b182bcde035ef0d691c
6ddd2549edfd65ec21fe54efae21e963b83fba1e
The text was updated successfully, but these errors were encountered: