Skip to content
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

Repo Indexer Type Bleve does not work with new migrated repositories. #16152

Closed
4 tasks
safag05 opened this issue Jun 14, 2021 · 4 comments
Closed
4 tasks

Repo Indexer Type Bleve does not work with new migrated repositories. #16152

safag05 opened this issue Jun 14, 2021 · 4 comments
Labels

Comments

@safag05
Copy link

safag05 commented Jun 14, 2021

  • Gitea version (or commit ref): 1.14.2
  • Git version: 2.26.3
  • Operating system: Custom Gitea Image, deployed via helm charts on Kubernetes.
  • Database (use [x]):
    • [ x] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • [x ] No

...

Hello,

After enabling REPO_INDEXER_ENABLED = true I have migrated a repository from Github and tried using Code Search feature on the UI to find a line from that repository however it did not return any output. After following the instructions from the Gitea discussions Code Search worked on the migrated repository. I looked through the issues on Github regarding this but did not find much about it. Is this something that can be worked on to automate the process so that we do not have to go inside the Kubernetes pod (in my case) and delete the "indexers" folder and reboot the pod in order for the changes to apply to the new migrated repositories after each migration?

My app.ini file
[indexer]
REPO_INDEXER_ENABLED = true

Thanks!

@lunny
Copy link
Member

lunny commented Jun 15, 2021

Maybe we should have a new event, repository migrated.

@lunny lunny added the type/bug label Jun 15, 2021
@safag05
Copy link
Author

safag05 commented Jun 16, 2021

@lunny Not sure what that means. Is this something that can be fixed easily?

@safag05
Copy link
Author

safag05 commented Jun 25, 2021

@lunny It seems that this was an issue before as well. Closed issue #9190. @MFYDev had the same issue with code search not working after migration. This issue was closed after some other fix related to code search but those fixes did not fix the original issue what @MFYDev described. I thought maybe this issue might help.

@lunny
Copy link
Member

lunny commented Sep 8, 2021

@safag05 Could you help to confirm that #16991 fix this?

6543 pushed a commit to 6543-forks/gitea that referenced this issue Sep 8, 2021
6543 pushed a commit to 6543-forks/gitea that referenced this issue Sep 8, 2021
zeripath pushed a commit that referenced this issue Sep 8, 2021
Fix #16986, #16152

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
zeripath pushed a commit that referenced this issue Sep 9, 2021
Fix #16986, #16152

Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
@lunny lunny closed this as completed Sep 9, 2021
@go-gitea go-gitea locked and limited conversation to collaborators Oct 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants