zoekt-git-index fails with indexGitRepo(...): reference not found about zoekt HOT 9 CLOSED

started failing for us

after an upgrade of anything, or just out of the blue?

from zoekt.

Not an upgrade, just out of the blue. But we figured it out: foo/foo-incident-starter is a completely empty repo, without any commits. If we delete it or add a commit, indexing works again.

from zoekt.

@hanwen Any ideas if this could be fixed?

from zoekt.

I added a test for indexing an empty repo in https://gerrit-review.googlesource.com/c/zoekt/+/313865

the test passes. I suspect something else is wrong. Can you delve a little bit deeper?

from zoekt.

Thanks! Changes in zoekt might have improved things since I opened this issue. I haven't actually seen this lately, but I'll investigate some more.

from zoekt.

I'll close this for now. Please reopen when you find something.

from zoekt.

@hanwen This failed for us again because of a new/empty repo. I haven't got any more debug data than the reference not found message above. We run zoekt againt Github Enterprise (v3.1.4), I don't know it that has anything to do with it.

from zoekt.

@hanwen This still fals. I'm not able to reopen this issue, should I make a new one?

from zoekt.

Maybe it actually works, but exits with a non-zero exit code when the indexGitRepo has been encountered? Because it continues indexing after the error has occured.

Our indexing script fails on non-zero exit codes, and thus aborts deployment of the new index. We would need to differentiate between an actual error and a non-error like this.

from zoekt.