I ran into something similar, for me I'd actually cloned the repository using the address without the git@ (something made it work). ClearML read it from the remote repository URL and used it. When I updated the URL of the remote repository in my git client it then worked.

EnviousPanda91 this seems like a specific issue with the clearml-task cli, could that be ?
Can you send a full clearml-task command-line to test ?

so we may use more specific lib/tool or just add a if-statement for case “ssh:git@”

I've tracked down our messages when this occurred and I think we had a different error to you, sorry.

In case it helps our problem was when the below command was run in the repository:
$ git remote -vReturned the https address rather than the ssh address.
Then clearml tried to convert this to the ssh address, which looked like
<org>/<repo>/rather than
:<org>/<repo>.git(Which is possible a separate bug?)

When I updated the URL of the remote repository in my git client

SuperiorPanda77 did you just replace “remote” for the client?

My remote in git client is ok:
ssh://git @<address>:5109<repo_path>.git
so I don’t understand why and where it changes :(

Hi AgitatedDove14 , I’m using clearml clearml-task to queue a task in a remote agent. The git remote URL is “ ssh://git@0.0.0.0:1234/path/to/repo.git ”, clearml https://github.com/allegroai/clearml/blob/aad01056b548660bb271c4f98447b715b8ba4c7d/clearml/backend_interface/task/repo/scriptinfo.py#L909 username from it (to cover cases like https://username@github.com/username/repository.git ), so the final URL is ssh://0.0.0.0:1234/path/to/repo.git , not ssh://git@0.0.0.0:1234/path/to/repo.git .