Unable to clone repository with submodule url [email protected]

[66li]

Bugs in the new version of go-git

Same as this problem description, it can be avoided by rolling back to version 3.4
go-git/go-git#397

[sarabala1979]

will wait go-git resolution go-git/go-git#397

[alexec]

fix: Relative submodules in git artifacts. Fixes #7141 (#7162)

[Hunter-Thompson]

I created a PR on go-github, lets wait and see. Hoping to get it merged ASAP since this bug breaks SSH cloning.

go-git/go-git#464

[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. Thank you for your contributions.

[Hunter-Thompson]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

keep

[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. Thank you for your contributions.

[Hunter-Thompson]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Keep

[Harishkrishna17]

@Hunter-Thompson Any update on this ?
Is there any workaround available

[Hunter-Thompson]

@Hunter-Thompson Any update on this ? Is there any workaround available

There is no work around, Id suggest going back to v3.2.4

[Harishkrishna17]

Rolling back to 3.2.4 causes the ssh issue for checkout of code from GitHub .

Issue :

You're using an RSA key with sha-1 , which is no longer allowed , please user a newer client or a different key type

[Harishkrishna17]

When is this pr going to be released ? any tentative date ?
Thanks

[tcolgate]

Can the go-git version being used not be rolled back within argo? This is a really painful break. I've spotted the merging of the forked version on master. Is there any chance that fix could be backported to a v3.3 point release? I'm working on migrating off of the docker executor and am basing that work on v3.3, but can't run it if this bug persists, (docker executor is slated to be removed in v3.4)

[tcolgate]

I've cherry picked 1d373c4 into 3.3.1 and rebuilt my executor image. The original "url can't contain colon" message has gone, but pulling the submodule still fails:

time="2022-04-12T07:08:53.994Z" level=error msg="executor error: artifact code failed to load: pkt-line 1: invalid hash text: encoding/hex: invalid byte: U+0052 'R' (ERR \n  myorg/myrepo.git/myorgl/mysubmod is not a valid repository name\n  Visit https://support.github.com/ for help)"