SFTP error upload no such file after update VS code 1.56.0

[Andika7]

Issue Type: Bug

while upload a file from local to remote, it show an error no such file and connection time out 10000. but the file is uploading without problem, just showing an error. This happen because I am update VS code version to 1.56.0.

Extension version: 1.12.9 VS Code version: Code 1.56.0 (cfa2e218100323074ac1948c885448fdf4de2a7f, 2021-05-04T22:09:06.405Z) OS version: Windows_NT x64 10.0.19041

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (4 x 2712)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|11.87GB (5.66GB free)| |Process Argv|--crash-reporter-id 1ad20214-094e-4571-829c-44d1a08acd9f| |Screen Reader|no| |VM|0%|

A/B Experiments

``` vsliv368cf:30146710 vsreu685:30147344 python383:30185418 pythonvspyt602cf:30294773 vspor879:30202332 vspor708:30202333 vspor363:30204092 pythonvspyt639:30291489 pythontb:30283811 pythonvspyt551:30291414 vspre833cf:30267465 pythonptprofiler:30281270 vscnewfiletext:30294816 vshan820:30294714 pythondataviewer:30285071 vscus158:30286553 vscgsv2ct:30294353 ```

[houguang]

[Evllis]

The same problem

Version: 1.56.0 (user setup) Commit: cfa2e218100323074ac1948c885448fdf4de2a7f Date: 2021-05-04T22:09:06.405Z Electron: 12.0.4 Chrome: 89.0.4389.114 Node.js: 14.16.0 V8: 8.9.255.24-electron.0 OS: Windows_NT x64 10.0.19041

[Evllis]

After looking at the questions from other users, it was suggested that vscode should be downgraded to 1.55 to solve the problem.

But I don't want to be demoted and wait for another way.

[yayaw]

[Evllis]

Well, just now I went to the remote server to have a look. Although it was said that there was an error prompt of no such file, the remote file has been updated, which does not affect the use.

[SebastianSava]

For now, you can change protocol from sftp to ftp, and port from 22 to 21. Just until get update :)

[Andika7]

Well, just now I went to the remote server to have a look. Although it was said that there was an error prompt of no such file, the remote file has been updated, which does not affect the use.

well, your right I will wait for the update

[Gforky]

Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.

[alteco-usa]

Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.

Be careful with it, some times, when you update file, is can come empty. And if update folder, some files can be empty, some files may contain text from other files. I downgraded my VSCode to previous version

[PolarAir]

Same problem here. The files have been uploaded successfully. Just 'set modify time' seems bugged

[Gforky]

Same issue here under version 1.12.9, pop up "No such file error" while uploading file to remote, but actually the file has been successfully uploaded.

Be careful with it, some times, when you update file, is can come empty. And if update folder, some files can be empty, some files may contain text from other files. I downgraded my VSCode to previous version

Thanks for your remind, this issue is annoying...

[anphxyz]

Same here! File upload well with 1 popup error!

[mastercrys]

Same problem here and cannot switch to ftp only mode and cannot downgrade le vscode version cause of infrastructure requirements. Please fix asap

EDIT: can confirm that the file is successfully uploaded even if the error appears

[duduheihei]

Meet the same problem

[ShachMaT]

This could be problem with SSH executable path.

Same error happens when you use Proxy command in ssh config and try connecting through terminal directly. Like this: ProxyCommand ssh -W %h:%p x@y

Doing like so: ProxyCommand C:\Windows\System32\OpenSSH\ssh.exe -W %h:%p x@y

Works.

Is there a setting for SSH executable path?!

[RadkoStulrajter]

Having the same issue. The extension is reporting error but the file is successfully uploaded to remote server:

[05-06 11:11:10] [error] Error: No such file at SFTPStream._transform (c:\Users\USER.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js:412:27) at SFTPStream.Transform._read (internal/streams/transform.js:205:10) at SFTPStream._read (c:\Users\USER.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\sftp.js:183:15) at SFTPStream.Transform._write (internal/streams/transform.js:193:12) at writeOrBuffer (internal/streams/writable.js:358:12) at SFTPStream.Writable.write (internal/streams/writable.js:303:10) at Channel.ondata (internal/streams/readable.js:719:22) at Channel.emit (events.js:315:20) at addChunk (internal/streams/readable.js:309:12) at readableAddChunk (internal/streams/readable.js:284:9) at Channel.Readable.push (internal/streams/readable.js:223:10) at SSH2Stream. (c:\Users\USER.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2\lib\Channel.js:167:15) at SSH2Stream.emit (events.js:315:20) at parsePacket (c:\Users\USER.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\ssh.js:3288:10) at SSH2Stream._transform (c:\Users\USER.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\ssh.js:694:13) at SSH2Stream.Transform._read (internal/streams/transform.js:205:10) at SSH2Stream._read (c:\Users\USER.vscode\extensions\liximomo.sftp-1.12.9\node_modules\ssh2-streams\lib\ssh.js:253:15) at SSH2Stream.Transform._write (internal/streams/transform.js:193:12) at writeOrBuffer (internal/streams/writable.js:358:12) at SSH2Stream.Writable.write (internal/streams/writable.js:303:10) at Socket.ondata (internal/streams/readable.js:719:22) at Socket.emit (events.js:315:20) at addChunk (internal/streams/readable.js:309:12) at readableAddChunk (internal/streams/readable.js:284:9) at Socket.Readable.push (internal/streams/readable.js:223:10) at TCP.onStreamRead (internal/stream_base_commons.js:188:23) when local ➞ remote c:\Users\USER\Desktop\WORKDIR\Projects!AUTOMATION\gst_dev\apps\p2mp_inventory.py

liximomo.sftp version v1.12.9

Version: 1.56.0 (user setup) Commit: cfa2e218100323074ac1948c885448fdf4de2a7f Date: 2021-05-04T22:09:06.405Z Electron: 12.0.4 Chrome: 89.0.4389.114 Node.js: 14.16.0 V8: 8.9.255.24-electron.0 OS: Windows_NT x64 10.0.18363

[raedlime]

Yeah, same for me. Hopefully it's gonna be fixed soon :-)

[myfender]

I have the same problem. MacBook Pro 16"

[dzw0218]

me too

[skoniks]

The same problem

[computertoucher]

Yeah this is annoying. And I'm not hoping for an update with 311 issues listed and the last commit 2 years ago... Is this extension abandoned?

[ghost]

VSCode was recently bumped to node v14. I looked deeper into other packages (ssh2, ssh2-streams) and it lead me to ssh2-sftp-client package. In the overview it says that the node itself had some changes with streams that causes these errors. Node v15.3 had additional changes (or a rollback) that fixes the issue.

In any way, this extension uses ssh2 and probably that's where the code should be updated and errors handled to work with node v14. I tried updating ssh2 package on this extension, but it didn't seem to help either. Most likely we'll have to wait until VSCode node is bumped to v15.

[tinusg]

I downgraded but here are some pointers on how to fix it temporarily: https://github.com/liximomo/vscode-sftp/issues/915#issuecomment-833269280

[mustadev]

same here. got this error after VSCode upgrade. is this plugin still maintained tho?. last update was 2019.

[slawn]

same here. got this error after VSCode upgrade. is this plugin still maintained tho?. last update was 2019.

good question - anybody knows the answer if that's still maintained or should I start looking for alternative?

[izversky]

It will be very sad to find out that the plugin has been abandoned :( I did not find a worthy alternative

[ghost]

After creating .ssh/config file:

[05-06 21:39:31] [warn] Can't set modified time to the file because Failure [05-06 21:39:31] [error] Error: No such file

[izversky]

[05-06 21:39:31] [warn] Can't set modified time to the file because Failure

This warning disappears after adding this property to the configuration: "profiles": {}

[ghost]

[05-06 21:39:31] [warn] Can't set modified time to the file because Failure

This warning disappears after adding this property to the configuration: "profiles": {}

In sftp.json? Not work.

[ghost]

All I want is to remove the useless notification sign.

[izversky]

[05-06 21:39:31] [warn] Can't set modified time to the file because Failure

This warning disappears after adding this property to the configuration: "profiles": {}

In sftp.json? Not work.

profiles only removes the warning, not the error.. Unfortunately Found info in another issue: #742

[Jany-M]

+1 @liximomo

[brunohl91]

Same problem here. Started after recent VS Code Update 1.56.0

[HDTran]

+1

[TheJohnLe]

+1

[caspahouzer]

+1

[jtapeg]

+1

[oneilonline]

Yup! So clearly this is a bug with SFTP since the last VSCode update 1.56.0. Glad to hear I'm not the only one! When is the fix coming out...???

[flahol]

Since VSCode update 1.56.0, same error message, however the file is copied

[lawrencejohnson]

I'm guessing with the repo untouched for 2 years we'll have to hope that the next VSCode update unbreaks it.

[oneilonline]

I'm guessing with the repo untouched for 2 years we'll have to hope that the next VSCode update unbreaks it.

WTF!?! ...and there is no alternative that's just as good. That's why I'm always weary and despise the plugin/extension model.

[lawrencejohnson]

I'm guessing with the repo untouched for 2 years we'll have to hope that the next VSCode update unbreaks it.

WTF!?! ...and there is no alternative that's just as good. That's why I'm always weary and despise the plugin/extension model.

You say that, but a lot of other people who say that also never donated to the owner of this repo. If I had to guess, they probably abandoned it because of all the issues people kept posting that were entirely connection/configuration related. That'd be exhausting work to do for free.

[jontobonto]

Have the same Problem :(

[satiromarra]

Editing the file: ~/.vscode/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js change the line 388: if (code === STATUS_CODE.OK) { to: if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) { Reload vscode It is not the most correct option but it works.

[oneilonline]

You say that, but a lot of other people who say that also never donated to the owner of this repo. If I had to guess, they probably abandoned it because of all the issues people kept posting that were entirely connection/configuration related. That'd be exhausting work to do for free.

I made my donation back when I started using it years ago. With that being said, getting in over your head or biting more off than you can chew, isn't a valid excuse to abandon something when people are relying on it and you to perform. If you do abandon it, perhaps it should be open source, community driven, or just give it to someone else to maintain/update.... oh wait, it's on github ;) LOL

[Evllis]

Editing the file: ~/.vscode/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js change the line 388: if (code === STATUS_CODE.OK) { to: if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) { Reload vscode It is not the most correct option but it works.

Yes, it's awesome.

[houguang]

Editing the file: ~/.vscode/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js change the line 388: if (code === STATUS_CODE.OK) { to: if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) { Reload vscode It is not the most correct option but it works.

cool

[zhixiangyao]

Editing the file: ~/.vscode/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js change the line 388: if (code === STATUS_CODE.OK) { to: if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) { Reload vscode It is not the most correct option but it works.

thx!!!

[zhixiangyao]

Editing the file: ~/.vscode/extensions/liximomo.sftp-1.12.9/node_modules/ssh2-streams/lib/sftp.js change the line 388: if (code === STATUS_CODE.OK) { to: if (code === STATUS_CODE.OK || code === STATUS_CODE.NO_SUCH_FILE) { Reload vscode It is not the most correct option but it works.

thx!!!

[error] Error: Failure😭

[DesistDaydream]

In fact, in addition to the No such file problem mentioned by everyone, there is another problem.

When I use the Upload Folder directives to upload a folder, some files will fail to upload. This situation did not exist before VSCode was updated.