We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've solved this already. I'm posting as a solution and also a problem, as its failure is not that clear
When I run
cml runner launch \ --token="..." \ --labels="cml-gpu" \ --idle-timeout="1h" --driver=github
I get
error: URL parsing failed. {"subject_url":"[email protected]:FR-DC/FRDC-ML.git\n"}
The problem is that CML doesn't recognize the SSH URLs (starts with git@), instead only works with HTTPS URLs (starts with https).
git@
https
To fix this, edit .git/config
.git/config
For example:
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = [email protected]:FR-DC/FRDC-ML.git
Change url = ... to the HTTPS variant
url = ...
[core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = https://github.com/FR-DC/FRDC-ML.git
This usually happens when you clone using SSH. It happened to me as I configured the gh-cli to prefer SSH, and can be a silent failure for many
gh-cli
gh repo clone OWNER/REPO
git clone [email protected]:OWNER/REPO.git
The text was updated successfully, but these errors were encountered:
I wonder if running cml ci first could solve this issue.
cml ci
Sorry, something went wrong.
$cml ci error: URL parsing failed. {"subject_url":"[email protected]/FR-DC/FRDC-ML.git\n"}
Unfortunately, it throws the same error if the URL is configured with SSH
No branches or pull requests
I've solved this already.
I'm posting as a solution and also a problem, as its failure is not that clear
Problem
When I run
I get
Solution
The problem is that CML doesn't recognize the SSH URLs (starts with
git@
), instead only works with HTTPS URLs (starts withhttps
).To fix this, edit
.git/config
For example:
Change
url = ...
to the HTTPS variantReplicating
This usually happens when you clone using SSH. It happened to me as I configured the
gh-cli
to prefer SSH, and can be a silent failure for manyThe text was updated successfully, but these errors were encountered: