I don’t see codebase files in the search results. The search results should include
the codebase files that include the search term I am searching with.
This is the URL to the search:
I am search for
Inside the repo, there are at least 15 files containing this phrase.
But the search returns none.
I am using gitlab.com.
I can’t test your link because I don’t have access to that project and group but I did another test on GitLab itself and it does work with a
. in the search field so I don’t think it’s related to that
blame_service.blame · Search · GitLab
And that’s not even related to the advanced search because you have it enabled on GitLab.com and I did a similar test on our instance with advanced search disabled and I can still find results when using a
. on the search field
Hi @zillemarco ,
Thank you very much for your response.
Would that be the cause that our repository is private and might not be indexed correctly by Gitlab.com?
I have a private repo and searched for something
firstword.secondword and it works fine. So it is not a limitation of private repos. Make sure for 100% what you are searching for is correct.
Thank you very much @iwalker for your response.
Unfortunately, I believe that I am searching for the right and existing thing.
Visual Studio Code search can locate all the files when searching for “Rails.cache”. But Gitlab.com does not.
I have also asked another engineer in the team to carry out the same search and they experienced the same problem.
To take it further, I see that search is failing to return accurate results for other search terms as well.
Do you believe that it might be a matter of triggering a whole rebuild of the search index? I don’t know whether this is something an admin of the Gitlab.com project can do.
Thank you very much in advance.
Is there any way i/we can issue a manual reindex for our project and / or group?
No, I see no options available for this. I neither see such a thing in my own instance from the web interface, but then I can run gitlab-rails commands to do reindexing. But this isn’t something you can do on Gitlab.com. And that is only for database reindexing, which might not necessarily help anyway with the issue you have.