[Bug][gitextract] crash when repository is empty

[galachad]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

The git extraction process crashes the server when the repository is empty.

This behavior was observed on GitLab. I am unsure if this issue occurs on other platforms. The container restarts because the process crashed, but I haven't found any errors in the logs.

time="2025-04-15 08:28:03" level=info msg=" [pipeline service] [pipeline #22] [task #9512] subtask Clone Git Repo finished in 38110 ms"
time="2025-04-15 08:28:03" level=info msg=" [pipeline service] [pipeline #22] [task #9512] finished step: 1 / 4"
time="2025-04-15 08:28:03" level=info msg=" [pipeline service] [pipeline #22] [task #9512] executing subtask Collect Commits"

executing subtask Collect Commits is the task that ends with crash.

What do you expect to happen

The git extraction task should fail, but instead it crashes.

How to reproduce

Try to scrap empty repository.

Anything else

No response

Version

v1.0.1

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[dosubot]

Hello @galachad! I'm Dosu, your friendly bot here to help with bugs, answer questions, and guide you as a contributor. I'm here to assist you while you wait for a human maintainer. How can I help you today?

The issue you're experiencing with the git extraction process crashing when encountering an empty repository might be related to how the process handles empty repositories. There is a mechanism in place to handle empty repositories by checking if a repository is empty using the repoIsEmpty function in the GitcliCloner struct. This function attempts to run the git log command, and if the repository is empty, it logs a warning and returns true, indicating that the repository is empty ^[1][2].

However, it seems that this mechanism might not be functioning correctly in your case, leading to a crash instead of a graceful failure. You might want to check if the useGoGit flag is set, as it can affect how empty repositories are handled. Additionally, ensure that the error handling in the GogitRepoCollector and related functions is correctly implemented to prevent crashes ^[3][4].

If the issue persists, consider adding additional logging to capture more detailed error messages, which could help in diagnosing the problem further.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}