SFTP speed issue marked as solved

This commit is contained in:
ChristianVisintin
2020-12-18 16:16:23 +01:00
parent 61b4a3b76e
commit 33683bc8ce
2 changed files with 5 additions and 2 deletions

View File

@@ -13,12 +13,17 @@
Released on ?? Released on ??
*The Bookmarks Update*
- **Bookmarks** - **Bookmarks**
- Bookmarks and recent connections are now displayed in the home page - Bookmarks and recent connections are now displayed in the home page
- Bookmarks are saved at - Bookmarks are saved at
- Linux: `/home/alice/.config/termscp/bookmarks.toml` - Linux: `/home/alice/.config/termscp/bookmarks.toml`
- Windows: `C:\Users\Alice\AppData\Roaming\termscp\bookmarks.toml` - Windows: `C:\Users\Alice\AppData\Roaming\termscp\bookmarks.toml`
- MacOS: `/Users/Alice/Library/Application Support/termscp/bookmarks.toml` - MacOS: `/Users/Alice/Library/Application Support/termscp/bookmarks.toml`
- Enhancements:
- File explorer:
- Log how long it took to upload/download a file
- Bugfix: - Bugfix:
- File mode of file on remote is now reported on local file after being downloaded (unix, linux, macos only) - File mode of file on remote is now reported on local file after being downloaded (unix, linux, macos only)
- Scp: when username was not provided, it didn't fallback to current username - Scp: when username was not provided, it didn't fallback to current username

View File

@@ -252,8 +252,6 @@ The developer documentation can be found on Rust Docs at <https://docs.rs/termsc
- Ftp: - Ftp:
- Time in explorer is `1 Jan 1970`, but shouldn't be: that's because chrono can't parse date in a different locale. So if your server has a locale different from the one on your machine, it won't be able to parse the date. - Time in explorer is `1 Jan 1970`, but shouldn't be: that's because chrono can't parse date in a different locale. So if your server has a locale different from the one on your machine, it won't be able to parse the date.
- Some servers don't work: yes, some kind of ftp server don't work correctly, sometimes it won't display any files in the directories, some other times uploading files will fail. Up to date, `vsftpd` is the only one server which I saw working correctly with TermSCP. Am I going to solve this? I'd like to, but it's not my fault at all. Unfortunately [rust-ftp](https://github.com/mattnenterprise/rust-ftp) is an abandoned project (up to 2020), indeed I had to patch many stuff by myself. I'll try to solve these issues, but it will take a long time. - Some servers don't work: yes, some kind of ftp server don't work correctly, sometimes it won't display any files in the directories, some other times uploading files will fail. Up to date, `vsftpd` is the only one server which I saw working correctly with TermSCP. Am I going to solve this? I'd like to, but it's not my fault at all. Unfortunately [rust-ftp](https://github.com/mattnenterprise/rust-ftp) is an abandoned project (up to 2020), indeed I had to patch many stuff by myself. I'll try to solve these issues, but it will take a long time.
- Sftp:
- sftp is much slower than scp: Okay this is an annoying issue, and again: not my fault. It seems there is an issue with [ssh2-rs](https://github.com/alexcrichton/ssh2-rs) library. If you want to stay up to date with the status of this issue, subscribe to [this issue](https://github.com/alexcrichton/ssh2-rs/issues/206)
- `NoSuchFileOrDirectory` on connect: let me guess, you're running on WSL and you've installed termscp through cargo. I know about this issue and it's a glitch of WSL I guess. Don't worry about it, just move the termscp executable into another PATH location, such as `/usr/bin`. - `NoSuchFileOrDirectory` on connect: let me guess, you're running on WSL and you've installed termscp through cargo. I know about this issue and it's a glitch of WSL I guess. Don't worry about it, just move the termscp executable into another PATH location, such as `/usr/bin`.
--- ---