-
Notifications
You must be signed in to change notification settings - Fork 28.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Core extensions not activating in remote session #196300
Comments
Same issue, we are unable to use Source Control, Copilot and other important features of VScode while developing on remote machine via SSH. |
We were able to fix this issue by updating our DataDog Agent and removing any remnants of dd-trace. I wish I had more detail on exactly what happened that caused this issue to occur. |
It's interesting that you mention this @mfann-or. We actually installed the Datadog agent on our server around the same time we began experiencing these issues. |
To provide the I notice that I am thinking they are injecting themselves to all nodejs runtimes via an env variable. Could you please share your env variables? |
@alexdima We managed to fix this today. We tried uninstalling the datadog-agent via apt-get remove datadog-agent but that didn't fix the issue. Eventually we discovered that datadog left some files in '/opt/datadog' we removed that dir and started to get this error in our terminal on every command: We were able to fix that error by editing the '/etc/ld.so.preload' file and deleting the line '/opt/datadog/apm/inject/launcher.preload.so'. It seems that when we had originally installed the agent as per the instructions here: https://app.datadoghq.com/account/settings/agent/latest?platform=ubuntu# Using the command: that option 'DD_APM_INSTRUMENTATION_ENABLED=host ' causes it to modify the '/etc/ld.so.preload' injecting dd-trace into the module loading. Subsequently reinstalling it without that option (the option was undesirable in our case anyway since we were using the agent to monitor external RDS databases and not the host running the agent) did not result in it modifying ''/etc/ld.so.preload' which is what broke vscode-server. |
ddtrace was installed via pip on our systems. Simply doing a |
@gduquesnay remove the |
This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines. Happy Coding! |
Type: Bug
After updating VSCode, some of the core extensions do not activate. This same error occurs on VS Code Insiders as well -- along with using the pre-release version of the Remote-SSH extension.
Errors shown in the Extension Host (Remote) logs:
VS Code version: Code 1.83.1 (f1b07bd, 2023-10-10T23:57:32.750Z)
OS version: Darwin arm64 23.0.0
Modes:
Remote OS version: Linux x64 4.18.0-477.27.1.el8_8.x86_64
Remote OS version: Linux x64 4.18.0-477.27.1.el8_8.x86_64
System Info
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
Extensions (16)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: