vscode-remote-workspace
vscode-remote-workspace copied to clipboard
mkloubert
Accessing files over sftp
Issue Type: Bug
When I acess files using sftp and say somehow the connection gets lost. There is no notification whatsoever from the vscode which says the connection is lost. I still am able to make changes to the files in the vscode but these changes are not reflected in the files in the server.
It would really great if there is some notification stating that the connection is lost.
I have many times ended up making changes to the files only to realize that the connection was lost and the changes are not reflected in the files.
VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:20:56.183Z) OS version: Linux x64 4.15.0-36-generic
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz (8 x 1335) |
| GPU Status | 2d_canvas: enabled checker_imaging: disabled_off flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software rasterization: disabled_software video_decode: unavailable_software video_encode: unavailable_software webgl: enabled webgl2: enabled |
| Load (avg) | 2, 1, 1 |
| Memory (System) | 15.39GB (8.11GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Extensions (11)
| Extension | Author (truncated) | Version |
|---|---|---|
| path-intellisense | chr | 1.4.2 |
| vscode-svgviewer | css | 1.4.7 |
| githistory | don | 0.4.3 |
| vscode-great-icons | emm | 2.1.44 |
| latex-workshop | Jam | 5.13.0 |
| vscode-remote-workspace | mkl | 0.36.5 |
| python | ms- | 2018.9.1 |
| sublime-keybindings | ms- | 4.0.0 |
| vscode-icons | rob | 7.27.0 |
| ayu | tea | 0.16.0 |
| better-align | wwm | 1.1.6 |
(3 theme extensions excluded)
I experience it too, It seems to happen with sftp. I tried fixing it with ?keepAlive=15 at the end of the URL, but it still does it.
I have exactly the same issue. adding a keepalive isn't working for me either.
same issue...it's pretty much unusable at this point...leave my sftp workstation idle for more than a few minutes and have to close and re-open to work again
