ftp - Error: XMKD not supported

[mihir-tunga]

Do you read the FAQ?

• [ x ] Yes.

Describe the bug
when trying to transfer a text file to a server (old) using ftp protocol (port 21) , I got the below error.
"Error: XMKD not supported"

and the trace as below:

at g (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:28508)
at p. (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:29232)
at p.emit (node:events:519:28)
at p._write (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:42069)
at writeOrBuffer (node:internal/streams/writable:564:12)
at _write (node:internal/streams/writable:493:10)
at Writable.write (node:internal/streams/writable:502:10)
at Socket.d (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:31604)
at Socket.emit (node:events:519:28)
at addChunk (node:internal/streams/readable:559:12)
at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
at Readable.push (node:internal/streams/readable:390:5)
at TCP.onStreamRead (node:internal/stream_base_commons:191:2

It appears from the error description, my ftp server does not support 'XMKD' command.
However, with standard command line ftp or FileZilla ftp client, I could transfer the file to the server.

I am wondering, if there is a way (workaround) in which I can transfer a text file to server that does not support XMKD command using ftp protocol.

I have a system specific constraint that forced me to use ftp protocol ( as opposed to sftp).

To Reproduce
Steps to reproduce the behavior:

1. Run command 'SFTP: Upload Active File
2. See error : Error: XMKD not supported"
   at g (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:28508)
   at p. (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:29232)
   at p.emit (node:events:519:28)
   at p._write (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:42069)
   at writeOrBuffer (node:internal/streams/writable:564:12)
   at _write (node:internal/streams/writable:493:10)
   at Writable.write (node:internal/streams/writable:502:10)
   at Socket.d (c:\Users\tunga.vscode\extensions\natizyskunk.sftp-1.16.3\dist\extension.js:2:31604)
   at Socket.emit (node:events:519:28)
   at addChunk (node:internal/streams/readable:559:12)
   at readableAddChunkPushByteMode (node:internal/streams/readable:510:3)
   at Readable.push (node:internal/streams/readable:390:5)
   at TCP.onStreamRead (node:internal/stream_base_commons:191:2
   Expected behavior
   A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. Mac, Win, Linux] - Windows
• VSCode Version [e.g. 1.51.0]
  Version: 1.93.1 (user setup)
  Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
  Date: 2024-09-11T17:20:05.685Z
  Electron: 30.4.0
  ElectronBuildId: 10073054
  Chromium: 124.0.6367.243
  Node.js: 20.15.1
  V8: 12.4.254.20-electron.0
  OS: Windows_NT x64 10.0.19045
• Extension Version [e.g. 1.7.0] - 1.16.3

Extension Logs from Startup - required

1. Open User Settings.

   • On Windows/Linux - File > Preferences > Settings
   • On macOS - Code > Preferences > Settings

2. Set sftp.debug to true and reload vscode.

3. Reproduce the problem, get the logs from View > Output > sftp.