Skip to content
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][Azure DevOps Go] fatal: Server does not support --shallow-since #7343

Closed
2 of 3 tasks
ichuniaiev opened this issue Apr 17, 2024 · 4 comments · Fixed by #7356
Closed
2 of 3 tasks

[Bug][Azure DevOps Go] fatal: Server does not support --shallow-since #7343

ichuniaiev opened this issue Apr 17, 2024 · 4 comments · Fixed by #7356
Assignees
Labels
type/bug This issue is a bug
Milestone

Comments

@ichuniaiev
Copy link

Search before asking

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

What happened

gitextractor log:

time="2024-04-17 11:11:20" level=error msg=" [pipeline service] [pipeline #1] [task #3] [Clone Git Repo] [gitcli] git exited with error\nstderr: Cloning into bare repository '/tmp/gitextractor2679208'...\nstderr: fatal: Server does not support --shallow-since\nstderr: fatal: the remote end hung up unexpectedly\n\n\tcaused by: exit status 128"
time="2024-04-17 11:11:20" level=error msg=" [pipeline service] [pipeline #1] [task #3] subtask Clone Git Repo ended unexpectedly\n\tWraps: (2) git exit error\n\tError types: (1) *hintdetail.withDetail (2) *errors.errorString"

What do you expect to happen

Repo is cloned and pipeline runs without errors

How to reproduce

Use Azure DevOps Go plugin and run pipeline

Anything else

It happens every execution

Version

v1.0.0-beta4

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

@ichuniaiev ichuniaiev added the type/bug This issue is a bug label Apr 17, 2024
@klesh klesh self-assigned this Apr 18, 2024
@klesh klesh added this to the v1.0 milestone Apr 18, 2024
@klesh
Copy link
Contributor

klesh commented Apr 18, 2024

Will fix it soon.

@abeizn
Copy link
Contributor

abeizn commented Apr 28, 2024

@ichuniaiev Already effective in v1.0.0-beta6

@ichuniaiev
Copy link
Author

ichuniaiev commented May 6, 2024

@klesh , @abeizn
I still get the same error on v1.0.0-beta6

time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] start executing task: 3"
time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] start plugin"
time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] [gitextractor.PrepareTaskData] UseGoGit: false"
time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] [gitextractor.PrepareTaskData] SkipCommitStat: false"
time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] [gitextractor.PrepareTaskData] SkipCommitFiles: true"
time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] total step: 4"
time="2024-05-06 09:34:53" level=info msg=" [pipeline service] [pipeline #1] [task #3] executing subtask Clone Git Repo"
time="2024-05-06 09:34:54" level=error msg=" [pipeline service] [pipeline #1] [task #3] [Clone Git Repo] [gitcli] git exited with error\nstderr: Cloning into bare repository '/tmp/gitextractor2289418913'...\nstderr: fatal: Server does not support --shallow-since\nstderr: fatal: the remote end hung up unexpectedly\n\n\tcaused by: exit status 128"
time="2024-05-06 09:34:54" level=info msg=" [pipeline service] [pipeline #1] [task #3] finished step: 1 / 4"
time="2024-05-06 09:34:54" level=info msg=" [pipeline service] [pipeline #1] [task #3] executing subtask Collect Commits"
time="2024-05-06 09:34:54" level=error msg=" [pipeline service] [pipeline #1] [task #3] run task failed with panic\n\tcaused by: run task failed with panic (github.com/apache/incubator-devlake/plugins/gitextractor/tasks.getGitRepo:87)\n\tWraps: (2) git repo is empty, please check subtask: clone repo\n\tError types: (1) *hintdetail.withDetail (2) *errors.errorString"

@klesh
Copy link
Contributor

klesh commented May 6, 2024

Aah.. I see. The fix was overwritten by this https://github.com/apache/incubator-devlake/pull/7364/files#diff-3847a66dd0632d39d27b84431808b867768544cc141ead4545f1d967fb31eea9L143 😂
Will create another PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/bug This issue is a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants