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

Error when cloning a repo #33

Closed
fslef opened this issue Dec 16, 2021 · 5 comments
Closed

Error when cloning a repo #33

fslef opened this issue Dec 16, 2021 · 5 comments

Comments

@fslef
Copy link

fslef commented Dec 16, 2021

Hello,

I run into this issue when I try to clone a repo:
image

This is my first try, I never used this extension before.

Could you help me to troubleshoot this issue ?

@SrBrahma
Copy link
Owner

Hi @fslef ! Is the repository in question public? Did you try it with other repositories?

@fslef
Copy link
Author

fslef commented Dec 17, 2021

I tried both, private and public repo, same behavior. But I need to clarify one point.

The error I'm facing is on MacOS system.
From Windows, same configuration same repo, I have no issues.

@SrBrahma
Copy link
Owner

I am also having this issue now, no idea why yet. Will look into it soon.

@SrBrahma
Copy link
Owner

SrBrahma commented Jan 19, 2022

Hi, it seems that I fixed it.

I am using git remote show <remoteUrl> inside the just git init'ed directory and parsing its stdout output to get the repo HEAD. It worked when the output was in English, but on other languages it wouldn't work. I changed the regex to get it when the line just contains HEAD and hopefully it shall now work with other languages.

Also, I've added the stdout to the error message you've got (and fixed the "haven't" to "hasn't" lol), so if you or someone else still has this issue, I will only need to change the regex to support the user language that it's failing.

Also, this didn't happened before on Prod for me. Maybe there was a git update that added my language to it. I still have no idea on why it didn't happen on Dev but only on Prod yesterday.

Sorry for the first bad experience you've had and I ask if you can give it another try and tell me if it's now working ;)

@SrBrahma
Copy link
Owner

I am closing it now as it is probably fixed. If it still happening for you or someone else, I ask to send here the error message, now improved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants