vscode icon indicating copy to clipboard operation
vscode copied to clipboard

Failed to get config from service: Failed to call "vscode-config": 500

Open MikaelHashiCorp opened this issue 10 months ago • 3 comments

Type: Bug

Issue troubleshooting has identified that the issue is with Visual Studio Code.

Error Message:

GitHub Copilot Workspace: Failed to get config from service: Failed to call "vscode-config": 500

Reproduction Steps:

  1. I launch Visual Studio Code.
  2. Visual Studio Code loads last workspace and last edited file.
  3. Visual Studio Code displays error message.
  4. This occures every time I close and open Visual Studio Code.

NOTE: This error did NOT occur with VS Code Insiders edition.

VS Code version: Code 1.97.2 (e54c774e0add60467559eb0d1e229c6452cf8447, 2025-02-12T23:20:35.343Z) OS version: Darwin arm64 24.3.0 Modes:

System Info
Item Value
CPUs Apple M3 Max (16 x 2400)
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
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Load (avg) 7, 7, 6
Memory (System) 64.00GB (5.99GB free)
Process Argv --crash-reporter-id 9aa17322-6799-465a-9d42-45d0acbb6be8
Screen Reader no
VM 0%
Extensions: none

MikaelHashiCorp avatar Feb 21 '25 19:02 MikaelHashiCorp

I get a slightly different error code: Failed to get config from service: Failed to call "vscode-config": 499

Moulick avatar Mar 02 '25 09:03 Moulick

Same, with 499. Happens only with "Github Copilot Workspace" extension. When I disable that, it goes away.

BorisAnthony avatar Mar 02 '25 23:03 BorisAnthony

same, spams a lot

keramblock avatar May 20 '25 13:05 keramblock

GitHub Copilot Workspace extension is about to be deprecated it seems. Thus, not much we can do in the vscode core experience to help here.

isidorn avatar May 29 '25 08:05 isidorn

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!