Symlinks are broken in SFTP
See original GitHub issueAtom Version: 1.4.3 System: Microsoft Windows 10 Enterprise Thrown From: Remote-FTP package, v0.7.16
Stack Trace
Uncaught TypeError: Cannot read property ‘isFile’ of undefined
At C:\Users\z269cjbb\.atom\packages\Remote-FTP\lib\connectors\sftp.js:155
TypeError: Cannot read property 'isFile' of undefined
at C:\Users\z269cjbb\.atom\packages\Remote-FTP\lib\connectors\sftp.js:155:21
at SFTPStream._transform (C:\Users\z269cjbb\.atom\packages\Remote-FTP\node_modules\ssh2\node_modules\ssh2-streams\lib\sftp.js:388:17)
at SFTPStream.Transform._read (_stream_transform.js:167:10)
at SFTPStream._read (C:\Users\z269cjbb\.atom\packages\Remote-FTP\node_modules\ssh2\node_modules\ssh2-streams\lib\sftp.js:173:15)
at SFTPStream.Transform._write (_stream_transform.js:155:12)
at doWrite (_stream_writable.js:292:12)
at writeOrBuffer (_stream_writable.js:278:5)
at SFTPStream.Writable.write (_stream_writable.js:207:11)
at Channel.ondata (_stream_readable.js:525:20)
at emitOne (events.js:77:13)
at Channel.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at Channel.Readable.push (_stream_readable.js:110:10)
at SSH2Stream.<anonymous> (C:\Users\z269cjbb\.atom\packages\Remote-FTP\node_modules\ssh2\lib\Channel.js:140:15)
at emitOne (events.js:77:13)
at SSH2Stream.emit (events.js:169:7)
at parsePacket (C:\Users\z269cjbb\.atom\packages\Remote-FTP\node_modules\ssh2\node_modules\ssh2-streams\lib\ssh.js:3163:10)
at SSH2Stream._transform (C:\Users\z269cjbb\.atom\packages\Remote-FTP\node_modules\ssh2\node_modules\ssh2-streams\lib\ssh.js:552:13)
at SSH2Stream.Transform._read (_stream_transform.js:167:10)
at SSH2Stream._read (C:\Users\z269cjbb\.atom\packages\Remote-FTP\node_modules\ssh2\node_modules\ssh2-streams\lib\ssh.js:213:15)
at SSH2Stream.Transform._write (_stream_transform.js:155:12)
at doWrite (_stream_writable.js:292:12)
at writeOrBuffer (_stream_writable.js:278:5)
at SSH2Stream.Writable.write (_stream_writable.js:207:11)
at Socket.ondata (_stream_readable.js:525:20)
at emitOne (events.js:77:13)
at Socket.emit (events.js:169:7)
at readableAddChunk (_stream_readable.js:146:16)
at Socket.Readable.push (_stream_readable.js:110:10)
at TCP.onread (net.js:523:20)
Commands
Config
{
"core": {}
}
Installed Packages
# User
minimap, v4.19.0
open-recent, v5.0.0
pigments, v0.23.1
Remote-FTP, v0.7.16
# Dev
No dev packages
Issue Analytics
- State:
- Created 8 years ago
- Comments:18
Top Results From Across the Web
sshfs breaks symlinks from SFTP server - Unix Stack Exchange
So this tells me the remote SFTP server is working fine (since I can create symlinks with a dedicated SFTP client), but for...
Read more >Sftp backend problems with symlinks - Suspected Bug
From my experience, there is a reason that symlinks generally don't work for a lot of commands as you'd have broken links everywhere...
Read more >SFTP: file symlinks in a jailed (chrooted) directory - Server Fault
I tried making a symlink (ln -s) to the desired directory but it does not work, as expected. I tried (cp -rl) to...
Read more >Support of symbolic links over SFTP - Google Groups
Not only are file-level symlinks still broken a year and a half later (!!!) but filenames aren't being escaped properly. I get errors...
Read more >sftp: please add support for symlinks #5011 - rclone ... - GitHub
Just hit this one myself while syncing from a source where SFTP is chrooted and most symlinks are broken. "-l" doesn't work on...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should be fixed in the latest release (v0.8.1), but try for yourself… Now
realpath
is used in order to resolve symlinks, which should handle relative symlinks in the right way.0.8.1 fixed the issue for me, no more error message either, thanks.