Vscode-gitlens: Extension disappeared

[catexis]

• GitLens Version: 8.5.6
• VSCode Version: 1.27.2
• OS Version: Linux Mint 19 Cinnamon 3.8.9 (core 4.15.0.34-generic)

After new reload of OS extension GitLens disappeared (screenshot)
I can't see any information in my source code, that provide this extension. Reinstallation this extension or vs code didn't apply any effect.

[eyalcohen4]

Same here, also reinstalled

OS Version: MacOS 10.13.5 (17F77) High Sieera
VSCode Version: 1.27.2
GitLens Version: 8.5.6

If there is any other information I could provide/help to triage, let me know!

[wirowka]

Same here, Windows 10 version 1709
VSCode Version: 1.27.2
GitLens Version: 8.5.6

[ihtiuh]

Same here, but this only happened for one of my git repository, I test with a new git repository and it worked fine though:

OS Version: openSUSE Leap 42.3
VSCode Version: 1.27.2
GitLens Version: 8.5

@eyalcohen4 May be you can update the settings.json with "gitlens.outputLevel": "verbose" and reload the workspace and check the Output window of GitLens.

For me it gets stuck at "Repository found in ... ":

Git found: 2.13.6 @ /usr/bin/git in 88 ms
Starting repository search in 1 folders
Searching for repositories (depth=1) in '_workspace path_' ...
Running("_workspace path_"): git rev-parse --show-toplevel
GitLens(v8.5.6) activated in 223 ms
Completed("_workspace path_"): git rev-parse --show-toplevel Completed in 105 ms
Repository found in "_workspace path_"

[eamodio]

Can all of you please enable output channel logging by setting "gitlens.outputLevel": "debug" in your settings.json. This will enable logging to the GitLens channel in the Output pane. Once enabled, please attempt to reproduce the issue (if possible) and attach the log lines from the GitLens channel.

[ihtiuh]

With "gitlens.outputLevel": "debug", for me the output is the same with as in the above comment.

[catexis]

In my output console same information. And one more thing: i get this problem in different computers.

Git found: 2.17.1 @ /usr/bin/git in 91 ms
Starting repository search in 1 folders
Searching for repositories (depth=1) in '<workspace_path>' ...
Running(<workspace_path>): git rev-parse --show-toplevel
GitLens(v8.5.6) activated in 213 ms
Completed(<workspace_path>): git rev-parse --show-toplevel Completed in 42 ms
Repository found in '<workspace_path>'

[vadviktor]

Is this related to #520 by any chance?

[catexis]

There is no antivirus on my linux systems.

[vadviktor]

@catexis, of course there is, https://www.clamav.net/ to name one. 😈

I saw you are using LM, but wanted to remind this thread to rule out the AV vector.

[catexis]

It seems that I have fixed a possible way to reproduce the situation. I use docker. Postgres image is connected to a data volume, which is a folder in the project folder. Even if this folder is added to .gitignore file, the extension responds to this situation. Perhaps, a large number of files prevents the initialization of the extension. After movig folder with postgres data to the parent directory extension was reappeared.

[eamodio]

@catexis interesting -- thanks for the extra info -- this gives me much more to go on.

[catexis]

@eamodio You're welcome! If i could give you more information - feel free to ask.

[gitsoft]

Same here

Windows 10 Pro, version 1803
VSCode Version: 1.28.1
GitLens Version: 8.5.6

[catexis]

Oh! I reproduced problem with 100% repeatability. It's only permission problem. For exhample, i have some folder:
Screenshot 01
Open this folder into vs_code:
Screenshot 02
Close folder and set some child folder permission through chmod like 0000:
Screenshot 03
Open this folder into vs_code:
Screenshot 04
@eamodio I think, that you can fix this problem by ignoring files and folders without permission for readwrite.

[eamodio]

@catexis when you repro the error -- if you turn on logging -- do you get any output in the GitLens output channel?

[catexis]

No any new information.
Screenshot 01
Git found: 2.17.1 @ /usr/bin/git in 13 ms Starting repository search in 1 folders Searching for repositories (depth=1) in '/home/anderson/some-dir' ... Running(/home/anderson/some-dir): git rev-parse --show-toplevel GitLens(v8.5.6) activated in 78 ms Completed(/home/anderson/some-dir): git rev-parse --show-toplevel Completed in 66 ms Repository found in '/home/anderson/some-dir'

[michaelgeorgeattard]

Antivirus deleted one of the extension's files. To fix issue on Windows:

• Remove GitLens extension from VSCode
• Reload VSCode
• Close all instances of VSCode
• Delete %userprofile%\.vscode\extensions\eamodio.gitlens-8.5.6
• Open VSCode
• Reinstall GitLens extension

[gitsoft]

I can confirm that the solution suggested by @michaelgeorgeattard works on windows.
As described above, you must manually delete %userprofile%.vscodeextensionseamodio.gitlens-8.5.6 during reinstall to make gitlens visible again.

Details
I never used the "Run as administrator" priviledge escalation function.
The version being uninstalled, manually deleted and reinstalled was GitLens Version: 8.5.6

[tnimni]

@michaelgeorgeattard thanks man that works great
for mac users:
remove the extension
reload vscode
go to setting.json by pressing cmd+shift+p > open user settings
delete all entries regarding the extension
close vs code
open vscode
install the extension

[eamodio]

I'm closing this -- as the main issue seems to be extension installation issue, which I cannot control (vscode handles extension installation).

[github-actions[bot]]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.