vscodium: Source Control died somehow

Today I discovered that version control began to visually duplicate the repositories in my workspace and any action with git ends with the error “” > git rev-parse --git-dir Opening repository for path='/home/work/projects/***' failed; ex=Error: Extension 'vscode.git' CANNOT use API proposal: scmValidation. Its package.json#enabledApiProposals-property declares: [] but NOT scmValidation. The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api vscode.git

I switched to VSCodium a few months ago so haven’t used VSCode since.

I’ve not found anything about “enabledApiProposals” error in documentation.

Unfortunately I haven’t steps to reproduce

OS: Ubuntu 20.04
Architecture x64
Version 1.65.2, 1.66.0

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 4
Comments: 41 (16 by maintainers)

Most upvoted comments

Hi All,

Managed to solve this. I have the latest version (1.66.1) installed with brew and after removing vscode.git-1.62.3 and vscode.git-base-1.64.0-next.68976705968 from ~/.vscode-oss/extensions everything started to work as it should.

You can close this issue I guess.

Thanks @mariusrugan and @daiyam !

istvnurbn on Apr 8, 2022

@AutumnRivers Yes, you should at least remove the git extension with rm ~/.vscode-oss/extensions/vscode.git-*. The best would be to remove all extensions by deleting the ~/.vscode-oss directory.

daiyam on May 8, 2022

So, I have this issue happening since recently on Debian 11, using

Version: 1.66.2
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-13T00:16:29.523Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Linux x64 5.10.0-13-amd64

I now have to delete vscode.git-1.62.3 from ~/.vscode-oss/extensions every time before I start. This doesn’t seem to be fixed for me.

cryham on Apr 25, 2022

the issue is not longer there, git works ok, thanks for your help @daiyam.

@istvnurbn maybe can confirm by disabling or deleting only the extension in ~/.vscode-oss/extensions or a complete cleanup (remove the ~/.vscode-oss)

mariusrugan on Apr 8, 2022

The next release will be out this Thursday and that issue will resolved there.

daiyam on May 2, 2022

jeanp413 on Apr 14, 2022

If found the main issue, VSCodium is updating the built-in extensions with extensions found on open-vsx.org when I think it shouldn’t do that. @mariusrugan It isn’t due to brew because I have the same behaviour with the .dmg

daiyam on Apr 8, 2022

@mariusrugan Now, is VSCodium working as it should?

daiyam on Apr 8, 2022

hold a bit, i didn’t clean ~/.vscode-oss every time.

mariusrugan on Apr 8, 2022

Not sure what happened… But the extension must be in ~/.vscode-oss/extensions, remove it. The correct one is the .app.

I’m opening an issue with openvsx to why the need for that extension…

daiyam on Apr 8, 2022

I wasn’t able to reproduce the issue but the upcoming 1.66.1 will have the missing extensions properties (#1040). So I think it should solve the issue. Please report if the 1.66.1 (when available) is fixing the issue or not. Thx

daiyam on Apr 7, 2022

The api have changed in v1.66. Today, I will look into it.

daiyam on Apr 7, 2022