Page MenuHomePhabricator

Index the slothslo gitlab repo in codesearch
Closed, ResolvedPublic

Description

Hi!

I would be nice to index the following SRE repositories in code search:

https://gitlab.wikimedia.org/repos/sre/slothslos
https://gitlab.wikimedia.org/repos/sre/sloth

They will be used by various teams to create and inspect SLOs, so it would be nice to have the code available in code search :)

Details

Event Timeline

Change #1304848 had a related patch set uploaded (by Dzahn; author: Dzahn):

[labs/codesearch@master] add repos/sre/sloth, repos/sre/slothslos to config

https://gerrit.wikimedia.org/r/1304848

Change #1304848 merged by Dzahn:

[labs/codesearch@master] add repos/sre/sloth, repos/sre/slothslos to config

https://gerrit.wikimedia.org/r/1304848

Mentioned in SAL (#wikimedia-operations) [2026-06-23T00:39:05Z] <mutante> codesearch10: systemctl start codesearch-write-config; systemctl restart hound-operations (gerrit:1304848) (T429819)

  • added to config with the change above
  • run puppet which git pulls
  • systemctl start codesearch-write-config to create new config
  • systemctl restart hound-operations.service
sudo journalctl -u hound-operations.service | grep sloth
Jun 23 00:48:55 codesearch10 docker[390836]: 2026/06/23 00:48:55 Searcher started for sre/sloth
Jun 23 00:48:56 codesearch10 docker[390836]: 2026/06/23 00:48:56 Searcher started for sre/slothslos

@Dzahn: did this change break all customisations to Codesearch somehow or is it something different that caused this? Compare

Since this is the only change in the last few days, seems suspicious.

@Dzahn: did this change break all customisations to Codesearch somehow or is it something different that caused this? Compare

Since this is the only change in the last few days, seems suspicious.

The post-merge job for the change (https://integration.wikimedia.org/ci/job/codesearch-pipeline-publish/190/console) failed due to T416707, might be related?

@Dzahn: did this change break all customisations to Codesearch somehow

This change did nothing besides adding 2 new repos to the index. So I am pretty confident the answer here is no.

You might mean T429828 though where codesearch was recreated from scratch and upgraded to trixie. This could be more likely to introduce some change.

But that being said, these customizations, that I am not aware of, must have happened on the client side or they were manual hacks because normally everything is managed by puppet or via the git repo.

The service was recreated from configuration management so if there were manual hacks then it would make sense they are gone but they would have to be re-applied and properly added to repositories. As I am not aware what they were I am afraid I can't do much here.

The post-merge job for the change (https://integration.wikimedia.org/ci/job/codesearch-pipeline-publish/190/console) failed due to T416707, might be related?

If some kind of customization was only applied by CI then at least I am not aware of that. I have reported the issue on the linked task though.

The CI problem has been solved by https://gerrit.wikimedia.org/r/c/labs/codesearch/+/1305248 because that newer image for go-lang did not reference mirrors.wikimedia.org

Seperately the UI customizations are back with details on the linked ticket above. (changing the proxy port to 3003 and making sure we go via hound_proxy, also rebuilt the codesearch-frontend image).