-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Git SCM issue ... #78809
Comments
Maybe info in #61491 (comment) can help you? |
What does You can also change the Log Level to Debug and see what Git tells you in the Output. |
Hi there, I have the same problem as @hemantwithu. My laptop is on windows but connect via remote-ssh to a linux server. When I open a directory which contains a git repository, I have the The output of I have not the same problem with the insider version. As you can see the regular vscode is updated to the very new July release 1.37.0. Other issues I am experiencing are regular disconnection from ssh and my python extension that won't start either. All those issues came at the same time as my git problem. |
@matmel It seems your extension host isn't running at all. Can you run @hemantwithu Still waiting on your answer. |
@joaomoreno Thanks for getting back at me. Here is the ouput of the developer tools console:
I am not sure but I may have corrupted somehow the remote host vscode server configuration when I changed my default git version by sourcing automatically in my bashrc the CentOS software collection sclo-git25. In other words, before the automatic sourcing I had:
and now:
|
FWIW, I deleted |
Issue Type: Bug
This issue has been occured multiple times showing a message "No source control providers registered" under source control. Though I can do the few git operation using command line but the basic featues on the files couldn't be done using command line such as file revision history and compare files.
I would really appreciate your help on this fix .
VS Code version: Code 1.37.0 (036a6b1, 2019-08-08T02:33:50.993Z)
OS version: Windows_NT x64 10.0.17134
The text was updated successfully, but these errors were encountered: