vscode: Remote Extension host terminated - Github Copilot Extension
Does this issue occur when all extensions are disabled?: Yes/No
CPUs | Intel® Core™ i5-1038NG7 CPU @ 2.00GHz (8 x 2000) |
---|---|
GPU Status | 2d_canvas: enabled canvas_oop_rasterization: disabled_off 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) | 2, 2, 3 |
Memory (System) | 16.00GB (0.02GB free) |
Process Argv | –crash-reporter-id c46b0ced-b526-4115-a328-36d485d6e30c |
Screen Reader | no |
VM | 0% |
I have seen a previous issue on this before but it was closed. I don’t see a resolution. I have disabled all extensions but Github Copilot and everything works fine. As soon as that extension is enabled and I open a python file, remote host crashes.
Steps to Reproduce:
Start
- when I attach vscode to a running docker container and I have GitHub copilot running. I get:
Remote Extension host terminated unexpectedly 3 times within the last 5 minutes.
- the extensions I have enabled on a fresh profile are pylance, python, dev containers, GitHub copilot.
my base docker image is pulling from FROM ubuntu:jammy-20230308
with nothing special going on except beyond some typical packages like git and curl, a pyenv. it was working about a month ago and just started acting up. I have started 3 fresh containers and all experience the issue immediately.
only other command I ran beyond the image is apt-get update && unminimize
About this issue
- Original URL
- State: open
- Created 9 months ago
- Reactions: 2
- Comments: 31 (8 by maintainers)
Mac users may find this workaround, referenced in another thread, helpful. The only other workaround that was working for me previously was downgrading.
The settings referenced are accessed from Docker > Settings > General.
I also have the same issue with the Rails project in docker environment. Same Copilot extension.
+1 for this … I have been waiting for like 6 months to find this fix @gloomylumi
This seems to be a big enough problem that it really should be called out by GitHub CoPilot, especially when paying for it.
VS Code is the last participant (uses GIT_ASKPASS environment variable) in the git authentication pipeline, as it’s crucial to honour the user’s auth settings. If the user has GCM configured, the auth request will never reach VS Code. If the auth request reaches VS Code, the git extension checks for registered credential providers, and if none exist for the remote a quick input widget is being shown to enter the username, password.
appears to affect vscode 1.82x and whatever version of GitHub copilot is required for that version (>v1.120.452)
I have manually installed 1.81 and disabled vscode update / extension updates and it is working just fine.
dev containers - v0.309.0 GitHub copilot - v1.120.452 pylance - v2023.9.30 python - v2023.14.0
another discussion with similar experience on python related copilot crashes.
https://github.com/orgs/community/discussions/61259
https://github.com/orgs/community/discussions/67644
More testing shows that when I open an html file for editing Copilot does not cause a remote extension crash but as soon as I open a python file it crashes. python 3.8.12