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
We are encountering an issue with the GitHub Copilot extension when using Visual Studio Code with Remote-SSH on an HPC login node. The extension works flawlessly with VS Code 1.93.0 (4849ca9) but fails on VS Code 1.95.3 (f1a4fb1). Interestingly, VS Code 1.95.3 works fine on the computing node of the same cluster, accessed via SSH forwarding from the login node.
To eliminate variables, we have tested the setup thoroughly:
Two personal computers were used:
One running VS Code 1.93.0.
The other running VS Code 1.95.3.
Both connect to the same HPC login node and same account using Remote-SSH.
Before each login, the .vscode-server directory on the remote machine was cleaned up to ensure a fresh environment.
On the remote machine, GitHub Copilot and GitHub Copilot Chat were the only extensions installed.
Expected Behavior
The GitHub Copilot extension should initialize and function correctly on both VS Code versions.
Actual Behavior
On VS Code 1.95.3, the Copilot extension causes the Extension Host process to crash only on the login node.
The issue does not occur on the computing node or when using VS Code 1.93.0 on the login node.
Disabling the GitHub Copilot extensions eliminates the issue.
Logs
Below are logs captured from the Extension Host (remote) process on both the login and computing nodes running VS Code 1.95.3. These logs highlight differences observed during initialization:
Network configuration remains the same across tests on both the login node and the computing node. Firewall are disable for all nodes.
The system administrator has confirmed that no OS-level rules (e.g., process termination) are in effect on the login node.
Key questions
Why it works on VS Code 1.93.0 but not on VS Code 1.95.3 ?
Why VS Code 1.95.3 works on our computing node but not on the login node?
VS Code version: Code 1.95.3 (f1a4fb1, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.0-78-generic
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)
Type: Bug
Description
We are encountering an issue with the GitHub Copilot extension when using Visual Studio Code with Remote-SSH on an HPC login node. The extension works flawlessly with VS Code 1.93.0 (4849ca9) but fails on VS Code 1.95.3 (f1a4fb1). Interestingly, VS Code 1.95.3 works fine on the computing node of the same cluster, accessed via SSH forwarding from the login node.
To eliminate variables, we have tested the setup thoroughly:
.vscode-server
directory on the remote machine was cleaned up to ensure a fresh environment.Expected Behavior
The GitHub Copilot extension should initialize and function correctly on both VS Code versions.
Actual Behavior
Logs
Below are logs captured from the Extension Host (remote) process on both the login and computing nodes running VS Code 1.95.3. These logs highlight differences observed during initialization:
Login Node (Fails)
Computing Node (Works)
Additional Notes
Key questions
VS Code version: Code 1.95.3 (f1a4fb1, 2024-11-13T14:50:04.152Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.0-78-generic
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
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
Extensions (7)
(1 theme extensions excluded)
A/B Experiments
The text was updated successfully, but these errors were encountered: