Git artifacts: 'reference delta not found' clone problem

[ghost]

Pre-requisites

• I have double-checked my configuration
• I can confirm the issues exists when I tested with :latest
• I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?

Looks like the library 'go-git' that you are using for cloning git repositories has a problem "reference delta not found" on the git.PlainClone function.

https://github.com/go-git/go-git/issues?q=is%3Aissue+reference+delta+not+found

Looks like in the latest version the problem is fixed. I think that a version update on your side will fix the problem.
Thank you!

Version

latest

Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.

artifacts:
          - name: repo
            path: /src
            git:
              repo: "{{workflow.parameters.repo}}"
              revision: "{{workflow.parameters.revision}}"
              disableSubmodules: true
              usernameSecret:
                name: "{{workflow.parameters.secretName}}"
                key: username
              passwordSecret:
                name: "{{workflow.parameters.secretName}}"
                key: password

Logs from the workflow controller

kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

ERRO[2022-12-13T10:08:07.481Z] container "main" in pod "create-flz2c-retrieve-changed-markdown-files-4256658970" is terminated  namespace=argo podName=create-flz2c-retrieve-changed-markdown-files-4256658970 workflow=create-flz2c

Logs from in your workflow's wait container

There are no logs

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is a mentoring request, please provide an update here. Thank you for your contributions.

[ivanspasov99]

Experiencing the same problem

[lvijnck]

I think this issue is still persisting, got it with the latest version, i.e., 3.4.4

[ghost]

I think this issue is still persisting, got it with the latest version, i.e., 3.4.4

There has not been a new release since the fix, i.e. it is not fixed in the 3.4.4 release, maybe in 3.4.5 (or what will be the next release version).
https://github.com/argoproj/argo-workflows/blob/release-3.4/go.mod#L229

[lvijnck]

Any work arounds known? This only seems to be the case for private repositories (I was able to pull a public one).

[rohankmr414]

@lvijnck This workaround by Alex might work for you until the fix for this issue is released. You can use your auth token as mentioned here.