VSCode can't sign in with GitHub and creates endless boxes in the "Source Control" panel

[Camto]

• Version: 1.54.1 (user setup)
• Commit: f30a9b7
• Date: 2021-03-04T22:38:31.419Z
• Electron: 11.3.0
• Chrome: 87.0.4280.141
• Node.js: 12.18.3
• V8: 8.7.220.31-electron.0
• OS: Windows_NT x64 10.0.18363

It doesn't stop making these little boxes in the "Source Control" panel. If I let it run, it eventually slows my computer to a crawl until I close VSCode.

It says I'm not signed in to any accounts. There was a moment when for no apparent reason it said I was signed in with GitHub (this was after the Live Share buttons stopped working, and even though it said I was signed in with GitHub they still did nothing). I signed out of it thinking it would remove any invalid sign in kind of state, but instead it went back to the regular broken state.

In a folder without a repo, there is an "Initialize Repository" button that effectively starts a repo and keeps making the little boxes. The "Publish to GitHub" button does absolutely nothing.

When I started reporting this bug, the "Share" button would let me sign in with Microsoft, and clicking to sign in with GitHub would say "Starting collaboration session: Auth token returned by github provider is empty." But after signing in and back out with Microsoft, neither button does anything.

Steps to Reproduce:

1. I don't know how it happened, just that it started when Live Share wasn't working properly. Disabling/uninstalling Live Share and GitHub extensions did nothing to help.

Does this issue occur when all extensions are disabled?: Yes

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• can't sign in (#117289)
• show providerId in list of sign ins? (#117497)
• Authentication: Sometimes Sign Out doesn't fully sign out (#104399)
• Aftering cancelling auth, signing in again shows error (#117098)
• Github sign in not working on Linux (#113163)

[suwayyah]

I have the same problem (without any live share) by opening any repository. Same for vs code insider 1.55. Reverting back to vscode 1.53.2 seems to be a good temporary solution.

[Camto]

Thanks, I'll just do that for now

[eamodio]

@suwayyah Can you provide more details on your setup os version, git version, etc or anything specially about those repos or how you are accessing them (e.g. remote?)?

[suwayyah]

W10 Enterprise 1909, 18363.1379 with git 2.29.2.windows.2 (I had git 2.22.x, I'm not sure anymore, had the same problem). I'm trying to access repos on github.molgen.mpg.de via my github enterprise account, e.g. https://github.molgen.mpg.de/nemeth/stmortality is public.

Originally, I thought that it might be our institute's network. But at the same time my own notebook can access these repos from our network with vscode 1.54.1 (w/ git 2.30.1 on W10) without any problem. Just to note, github desktop app works fine on both computers. And as I mentioned before, vscode 1.53.2 has no problems either.

[eamodio]

@suwayyah Thanks for the extra details. I've tried your repository, and I can't reproduce the problem. Is there any steps that you can provide? How do you open vscode? etc?

[eamodio]

Can you also post the output from the Git output channel? I want to see if there are multiple Open repository: lines or something like that

[hamza512b]

This only happens for me when I open Vscode using Git Bash command.

This is the output of git:

> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir
> git rev-parse --git-dir

[eamodio]

What is the output of git rev-parse --git-dir if your run it from the same folder you are opening in VS Code?

[hamza512b]

It outputs: .git

$ git rev-parse --git-dir
.git

[eamodio]

Does it still happen if you disable all extensions?

[hamza512b]

Yep, it does still happen after disabling all extensions.

[eamodio]

@hamzakhuswan so you are just typing code . in Git Bash? or?

[hamza512b]

@hamzakhuswan so you are just typing code . in Git Bash? or?

Yeah, exactly

[suwayyah]

I usually open my vscode from github desktop (repository/open in vscode) or from windows explorer context menu (open with code) . I can share the git output tomorrow.

[eamodio]

Does the same thing reproduce on the latest Insiders edition?

[suwayyah]

Yes, I think I mentioned the version as well earlier.

[suwayyah]

Git output when vscode opens on Explorer tab:
Looking for git in: C:\Program Files\Git\cmd\git.exe
Using git 2.29.2.windows.2 from C:\Program Files\Git\cmd\git.exe

git rev-parse --git-dir
git rev-parse --git-dir
git rev-parse --git-dir
git rev-parse --git-dir
git status -z -u
git status -z -u
git status -z -u
git symbolic-ref --short HEAD
git symbolic-ref --short HEAD
git symbolic-ref --short HEAD
git for-each-ref --format=%(refname)%00%(upstream:short)%00%(upstream:track)%00%(objectname) refs/heads/master refs/remotes/master
git for-each-ref --format=%(refname)%00%(upstream:short)%00%(upstream:track)%00%(objectname) refs/heads/master refs/remotes/master
git for-each-ref --format=%(refname)%00%(upstream:short)%00%(upstream:track)%00%(objectname) refs/heads/master refs/remotes/master
git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname)
git remote --verbose
git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname)
git remote --verbose
git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname)
git remote --verbose
git rev-parse --git-dir
git rev-parse --git-dir
git rev-parse --git-dir

if I click on the source control tab then 'git rev-parse --git-dir' endlessly repeats in addition

[suwayyah]

Opening vscode again same way on same repo:
Looking for git in: C:\Program Files\Git\cmd\git.exe
Using git 2.29.2.windows.2 from C:\Program Files\Git\cmd\git.exe

git rev-parse --git-dir
git rev-parse --git-dir
git rev-parse --git-dir
git rev-parse --git-dir
git rev-parse --git-dir

initially on the explorer tab

[eamodio]

I've pushed a logging change coming in the latest insiders (should be released relatively soon). Hopefully that will help pinpoint things better.

[z387-hq]

In latest Insiders with Git 2.30.2:

> git rev-parse --git-dir
Opening repository for path='D:\Git\a' failed; ex=Error: [nullExtensionDescription]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api nullExtensionDescription
> git rev-parse --git-dir
Opening repository for path='D:\Git\b' failed; ex=Error: [nullExtensionDescription]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api nullExtensionDescription
> git rev-parse --git-dir
Opening repository for path='D:\Git\c' failed; ex=Error: [nullExtensionDescription]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api nullExtensionDescription

[suwayyah]

Looking for git in: C:\Program Files\Git\cmd\git.exe
Using git 2.29.2.windows.2 from C:\Program Files\Git\cmd\git.exe
> git rev-parse --git-dir
Opening repository for path='u:\git\nemeth\stmortality' failed; ex=Error: [nullExtensionDescription]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api nullExtensionDescription
Opening repository for path='u:\git\nemeth\stmortality\app.R' failed; ex=spawn C:\Program Files\Git\cmd\git.exe ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn C:\Program Files\Git\cmd\git.exe ENOENT
	at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
	at onErrorNT (internal/child_process.js:469:16)
	at processTicksAndRejections (internal/process/task_queues.js:84:21)
Opening repository for path='u:\git\nemeth\stmortality\LICENSE' failed; ex=spawn C:\Program Files\Git\cmd\git.exe ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn C:\Program Files\Git\cmd\git.exe ENOENT
	at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
	at onErrorNT (internal/child_process.js:469:16)
	at processTicksAndRejections (internal/process/task_queues.js:84:21)
Opening repository for path='u:\git\nemeth\stmortality\README.md' failed; ex=spawn C:\Program Files\Git\cmd\git.exe ENOENT {
  "gitErrorCode": "NotAGitRepository"
}Error: spawn C:\Program Files\Git\cmd\git.exe ENOENT
	at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
	at onErrorNT (internal/child_process.js:469:16)
	at processTicksAndRejections (internal/process/task_queues.js:84:21)
> git rev-parse --git-dir
Opening repository for path='u:\git\nemeth\stmortality\www' failed; ex=Error: [nullExtensionDescription]: Proposed API is only available when running out of dev or with the following command line switch: --enable-proposed-api nullExtensionDescription

[z387-hq]

Related?

• Remote-SSH does not work with 1.54 and --extensions-dir option (#118812)
  

[NicolaSpadari]

Same thing happened here. Not using live share feature, just popped out of no where.
Tried reinstalling vscode and git, it fixed, the next change I made triggered this duplication bug again, output console is empty for me. Happend with extensions and also whithout them.

Edit: I can confirm downgrading to 1.53.2 fixes the issue. Probably related to the update itself

[suwayyah]

Still present as of:
Version: 1.55.0-insider (user setup)
Commit: 84fe402
Date: 2021-03-15T05:14:29.836Z
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Windows_NT x64 10.0.18363

[eamodio]

If you look in the Log (Extension Host) output channel do you see any lines like "Could not identify extension for ‘vscode’ require call from"?

Also can you provide the logs from the Git output channel?

[suwayyah]

There is a warning on Could not identify extension for vscode require call from

[eamodio]

@suwayyah Thanks! I believe this is another case of #118562. Which will be fixed in the next insiders and in the 1.54.3 recovery release (which should be out tomorrow)

[suwayyah]

Looks good on 1.54.3, thanks!

[pattarika]

Just upgrade to 1.54.3 Very happy with this. Thanks!

[Camto]

Works for me too now!

[eschweighofer]

it works again in 1.54.3, Thanks