[BUG] Authentication Error, Not Handled Correctly

[Danc2050]

[BUG] Authentication Error, Not Handled Correctly

[jgottschlich]

Hi @Danc2050 - thanks so much for reporting this to us. @nhasabni and I will take a look at it immediately!

Best,
The ControlFlag Team

[Danc2050]

I think perhaps some of these repos

a) no longer exist
b) are private

The Repository not found message is common:

remote: Repository not found.
fatal: Authentication failed for 'https://github.com/nefarius/ViGEm/'
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/ulli-kroll/mt7610u/'
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/muennich/mupdf/'
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/concurrent-php/ext-async/'
remote: Repository not found.
fatal: Authentication failed for 'https://github.com/ddevault/aerc/'

And when I navigate to the links here I indeed see no repositories (sometimes not even a user). I will give an update of all the repositories that are no longer valid later.

[Danc2050]

Here are the list as promised. Some have been taken down due to copyright issues.
non_existant_repos.txt

I ran into another issue where my system is suddenly saying everything is read-only and my WSL 2 is bricked. This could be some issue with WSL, so I won't forward any details and keep the context of this issue same.

[nhasabni]

Hi @Danc2050,

Thanks for the report and analysis. We found that some of the repositories are non-existent (as you also found), and for some reason, git clone asks for credentials for such repositories. Different versions of git seem to have different mechanisms to deal with this problem, but we found that adding -c core.askPass=echo to git clone command helps with the problem. For non-existent repositories, it will simply report an error and continue rather than waiting for username/password.

PR #34 should fix this issue. Do you want to give it a try? Let us know.

Thanks,
The ControlFlag team