-
Notifications
You must be signed in to change notification settings - Fork 505
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
[Bug][GitHub] GitExtractor fails on empty repository due to shallow clone #7468
Comments
Thanks for reporting the problem, will look into it ASAP |
@klesh FYI the fix on #7475 causes this in some repos:
Running with this image release-v1.0_240516_0721_3ae23bf (I was testing the Jenkins fix I did). I increased the time range but no luck. |
@gustavobini Thanks for reporting the problem. |
@gustavobini Can you share some of them if possible? I am having trouble to reproduce the problem. |
@klesh they're private org repos. Let me see what I can do. |
@klesh I cloned the repo locally and executed the same commands Devlake does, and my issue is exactly the same as this one https://stackoverflow.com/questions/63878612/git-fatal-error-in-object-unshallow-sha-1 and also got resolved by |
@gustavobini Thanks for the information. Will submit another PR to fix the problem even though I do not fully understand why... 🤣 |
Search before asking
What happened
When syncing GitHub, a few repositories had errors as they were cloned with
--bare --shallow-since=2024-03-09T13:24:51Z
and the last commit on these repositories was over 3 months before the date.What do you expect to happen
I expected a warning to be shown and not an error, as it's expected for the extractor to not do anything if there's no repository.
How to reproduce
Set the sync policy to only include the last day and sync a GitHub repository with changes before that date.
Anything else
Version
v1.0.0-beta7
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: