vscode: git commit generates error dialog and git extension reports uncaught errors

Type: Bug

When I commit from the git extension, I frequently get an error message that “Git: Extention ‘vscode.git’ CANNOT use API proposal: telemetry”.

When I look at “Running Extensions”, git reports 32 uncaught errors.

I do not know if the two error counts are related.

This only recently started happening (last couple of weeks).

VS Code version: Code 1.85.1 (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:49:37.021Z) OS version: Windows_NT x64 10.0.26020 Modes: Remote OS version: Linux x64 5.15.90.1-microsoft-standard-WSL2

System Info
Item Value
CPUs 11th Gen Intel® Core™ i7-11370H @ 3.30GHz (8 x 3302)
GPU Status 2d_canvas: enabled
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) undefined
Memory (System) 31.84GB (7.30GB free)
Process Argv –folder-uri=vscode-remote://wsl+Ubuntu-22.04/home/brad/stpm --remote=wsl+Ubuntu-22.04 --crash-reporter-id 599da817-f9ce-4935-b18c-03818c17620d
Screen Reader no
VM 0%
Item Value
Remote Dev Container
OS Linux x64 5.15.90.1-microsoft-standard-WSL2
CPUs 11th Gen Intel® Core™ i7-11370H @ 3.30GHz (8 x 3302)
Memory (System) 15.54GB (12.97GB free)
VM 0%
Extensions (13)
Extension Author (truncated) Version
remote-containers ms- 0.327.0
remote-wsl ms- 0.81.8
rewrap stk 1.16.3
markdown-table-prettify dar 3.6.0
vscode-markdownlint Dav 0.53.0
git-graph mhu 1.30.0
python ms- 2023.22.1
vscode-pylance ms- 2023.12.1
cmake-tools ms- 1.16.32
cpptools ms- 1.18.5
rewrap stk 1.16.3
cmake twx 0.0.17
markdown-all-in-one yzh 3.6.1
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
vsclangdc:30486549
c4g48928:30535728
azure-dev_surveyone:30548225
0bi6i642:30933247
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232

About this issue

  • Original URL
  • State: closed
  • Created 6 months ago
  • Comments: 18 (6 by maintainers)

Most upvoted comments

SOLVED For me, I found out it was because I was on a detached head on Git. For some reason, reattaching to master solved it.

Thanks @bradlitterell. Fix for this will be in Monday’s VS Code Insiders release. Apologies for the inconvenience!

+1 for gilad905’s suggestion. I was able to easily repro the problem:

  1. create new repo from command line.
  2. make first commit.
  3. check out main
  4. edit and commit from git source-control panel in vscode, works.
  5. check out the new head (the second commit), detached.
  6. make another change and try to commit it in vs code

Expected: It works correctly Actual: The commit is created in the repository, but the “telemetry” error message shown above appears.