You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
🐛 Describe the bug
This error is reported when I launch VSCodium on one of my two hosts. Happens consistently on that host only – the two hosts correspond to two users on the same Ubuntu device, so they use the same VSCodium installation but each has its own config and set of external extensions.
Adding "git-ui" to "ignoreExtensions" in syncLocalSettings.json prevents this error, as one would expect. However, shouldn't Settings Sync exclude it automatically, since git-ui is built into VSCode/VSCodium?
🌴 Visual Studio Code VSCodium Version : [ 1.79.2 ]
🌴 Code Settings Sync Version : [ 3.4.3 ]
🌴 Standard or Insiders : [ Standard ]
🌴 Portable or Installed : [ Installed ]
🌴 OSS or Official Build : [ OSS ]
🌴 Operating System : [ Kubuntu 22.04 ]
🌴 Occurs On: [ Download ]
🌴 Proxy Enabled: [ No ]
🌴 Gist Id: [ faab2abf9363cdd4b508005a47b13b3f ]
📰 To Reproduce
Steps to reproduce the behavior:
Configure Settings Sync on 2 hosts
Upload from host 1 – output shows git-ui among the extensions uploaded.
Download on host 2.
See error.
💪 Expected behavior
Settings Sync does not (try to) upload/download git-ui since it is a built-in extension.
ERR Extension 'vscode.git-ui' not found.: Error: Extension 'vscode.git-ui' not found.
at handler (vscode-file://vscode-app/usr/share/codium/resources/app/out/vs/workbench/workbench.desktop.main.js:2604:42800)
workbench.desktop.main.js:624 ERR [Extension Host] Error: Error: Error: Extension 'vscode.git-ui' not found.
at /home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:22293
at /home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:11611
at Object.throw (/home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:11716)
at s (/home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:10513)
workbench.desktop.main.js:97 [Extension Host] Error: Error: Error: Extension 'vscode.git-ui' not found.
at /home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:22293
at /home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:11611
at Object.throw (/home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:11716)
at s (/home/userx/.vscode-oss/extensions/shan.code-settings-sync-3.4.3-universal/out/extension.js:290:10513)
I @ workbench.desktop.main.js:97
workbench.desktop.main.js:759 Sync: Error Logged In Console (Help menu > Toggle Developer Tools).
OUTPUT:
Realtime Extension Download Summary
--------------------
TOTAL EXTENSIONS : 2
[x] - EXTENSION: git-ui - INSTALLING
📺 Additional context
Will try to provide upon request.
The text was updated successfully, but these errors were encountered:
🐛 Describe the bug
This error is reported when I launch VSCodium on one of my two hosts. Happens consistently on that host only – the two hosts correspond to two users on the same Ubuntu device, so they use the same VSCodium installation but each has its own config and set of external extensions.
Secondly, the download stops when the error happens – apparently a separate issue.
Adding
"git-ui"
to"ignoreExtensions"
insyncLocalSettings.json
prevents this error, as one would expect. However, shouldn't Settings Sync exclude it automatically, sincegit-ui
is built into VSCode/VSCodium?🌴
Visual Studio CodeVSCodium Version : [ 1.79.2 ]🌴 Code Settings Sync Version : [ 3.4.3 ]
🌴 Standard or Insiders : [ Standard ]
🌴 Portable or Installed : [ Installed ]
🌴 OSS or Official Build : [ OSS ]
🌴 Operating System : [ Kubuntu 22.04 ]
🌴 Occurs On: [ Download ]
🌴 Proxy Enabled: [ No ]
🌴 Gist Id: [ faab2abf9363cdd4b508005a47b13b3f ]
📰 To Reproduce
Steps to reproduce the behavior:
git-ui
among the extensions uploaded.💪 Expected behavior
git-ui
since it is a built-in extension.📺 Console Error Log
📺 Additional context
Will try to provide upon request.
The text was updated successfully, but these errors were encountered: