Installed, but can't execute

[SiTaggart]

Has anyone seen this before? GitLens has stopped working for me, and removing and reinstalling hasn't made any difference. If I turn on verbose logging for GitLens, nothing is logged, it's like it's completely not running in VS Code.

I even tried showing the welcome screen using the command palette in VS Code, and it presented me with the above error command 'gitLens.showWelcomePage' not found.

It used to work on this machine, it was great. Only recently noticed it stopped, I'm not often in VS Code these days so I don't exactly know when it stopped working. I'm stumped.

• GitLens Version: 8.1.1
• VSCode Version: 1.21.1
• OS Version: MacOS 10.13.3

Steps to Reproduce:

1. Install GitLens

[eamodio]

I willing to bet this is an installation issue. Could you try removing GitLens again, completely exit all instances of vscode, start vscode, exit vscode. Then verify that in ~/.vscode/extensions there are no folders that start with eamodio.gitlens-. If there are please remove them. After that you should be able to start vscode and install GitLens again.

Please let me know if this helps.

[aghecht]

I'm getting the same issue on Linux Mint 18.3 with GitLens version 8.1.1 and VSCode 1.21.1. I wiped out the extensions directory and even all my local settings, but that didn't resolve the problem. In addition to that error, GitLens isn't showing up on Explorer. There is no option to display it.

I downloaded and installed a copy of 8.1.0, and that works without any problems.

[eamodio]

@aghecht Thank you for the additional information! If you open the devtools (Developer: Toggle Developer Tools from the command palette) do you see any errors in the console? If so can you post them here?

Thanks!

[aghecht]

@eamodio

I was seeing a 'could not parse package.json' error. I looked at the directory, and this is what I saw:

I'm not sure how those files got zeroed out.

Edit: Tried reinstalling the latest version and it worked. Weird. VSCode is my primary editor, so I'll look at the contents again if/when GitLens stops working again.

[eamodio]

@aghecht are you installing GitLens from the marketplace or from the vsix directly? (for the 8.1.1 version)

[aghecht]

@eamodio I installed 8.1.1 from the marketplace. The previous versions were installed directly by extracting the contents of the install file and copying over the 'extension' directory.

[eamodio]

Could you try downloading 8.1.1 from GitHub and then when everything is clean, use vscode's built-in support for installing a vsix and see if that works? You can access it via the ... menu in the extensions pane

[SiTaggart]

@eamodio Yup, I had to uninstall it from VS Code, and I noticed the folder was still present in .vscode/extensions/. I manually removed that, opened VS and reinstalled the package and it worked again. Thanks, I should have tried that myself!

[aghecht]

@eamodio Downloading 8.1.1 from GitHub and installing the vsix file works.

[eamodio]

@aghecht I'm so confused 😕 — there seems to be some bad behavior with extension installation lately. So both vsix work, but installing from the marketplace still doesn't?

[aghecht]

@eamodio You and me both. I have been seeing a little bit of weirdness with extension installation over the past week. GitLens is one of my most used plugins, which is why I would notice it first.