-
Notifications
You must be signed in to change notification settings - Fork 0
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
Type: <b>Bug</b> #2
Comments
|
Type: Bug
I have a central computer I connect to devices on the shopfloor which do not have internet connection as well as servers that have internet connection. They are all linux based (ubuntu or raspian rpi4).
Starting from Version 1.90 I cannot ssh-connect to the shopfloor devices anymore with vscode (other ssh connections e.g. mobaxterm work just fine).
vscode is asking for password is trying to "download" (probably something from the internet). Then (presumaply) times out and asks me to enter the password again. repeat. This is on all shopfloor devices.
When I try to connect the same way to a computer which has internet connection it works just fine.
I have tried to delete the whole ~/.vscode-server directory on the target machine with the intent to "reset" the connection. Yet the same issue.
With this VSCode has become pretty useless in environments when there is no internet connection of the ssh-target device.
VS Code version: Code 1.90.0 (89de5a8d4d6205e5b11647eb6a74844ca23d2573, 2024-06-04T19:33:54.889Z)
OS version: Windows_NT x64 10.0.20348
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: unavailable_software
Extensions (7)
A/B Experiments
Publicación original de @akrea en microsoft/vscode#215436
The text was updated successfully, but these errors were encountered: