WindTerm
WindTerm copied to clipboard
There is a bug in downloading large files in the latest version 2.6.0
The latest released version will damage the file when downloading large files. I downloaded it on two different servers and the file was damaged. Moreover, the md5 of the damaged file is consistent, so I don’t know if it is multi-threaded. Caused by fragmented download, mobaxterm download is normal
me too
All download files are damaged
Me too, so I downloaded tar.gz several times and couldn't extract it.
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding 2
megabytes are considered large files. Due to the use of AIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.
I will fix it as soon as possible. Also, please let me know which version has the issue, Windows
, macOS
, or Linux
? Thank you.
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.
windows2.6 release, 10 Prerelease no problem
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.
In fact, both Windows and Linux 2.6 release versions have this problem, and the Mac version has no test conditions.
source
.tar.gz use Linux version download
.tar.tgz use Windows version download
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.
windows10 WindTerm_2.6.0_Windows_Portable_x86_32.zip
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.
Windpws11 WindTerm_2.6.0_Windows_Portable_x86_64.zip
me too. md5 is different
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.
Windows 11, WindTerm_2.6.0_Windows_Portable_x86_64.zip
me too, Use the hex tool to open it and find that it is all data 0 version: WindTerm_2.6.0_Windows_Portable_x86_64.zip
Same problem Windows 10, MacOS 11.7.9 WT 2.6
I've encountered hash inconsistency issues on Manjaro (Linux), which is causing significant trouble for me, particularly because I need to retrieve large backup files from the server.
As a temporary solution, I'm considering downgrading to version 2.5.0. However, I'm concerned about the integrity of my configuration file. Will the downgrade potentially corrupt it?
me too!!!
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.
macOS 12.7 WindTerm 2.6.0
same issue here. OS: Windows 11 Professional (10.0.22631) WindTerm: 2.6.0
+1
Same issue on 2.6.0 using macos
期待修复
MacOs 13.6.4 2.6.0上面下载的文件损坏
same here :(
Windows 11 Pro Version 23H2 OS build 22631.3155 Processor 11th Gen Intel Core i7-1165G7 @ 2.80GHz System type 64-bit operating system, x64-based processor
Does the author have a repair plan, or should they simply revert back to the old version for use?
Me too, the large files with size 0 and small files besides texts are damaged/broken. I was suspecting the transfer MODE but cannot find a way to change the transfer mode from ASCII to BINARY.
Waiting for the fix. Same issue on Arch
Same issue on windows 2.6.0 release.
same
Indeed, different writing strategies are adopted for the downloading of large files and small files and files exceeding
2
megabytes are considered large files. Due to the use ofAIO+O_DIRECT+O_SYNC
, the large file needs to be manually resized to the correct size upon completion of the download, and this step is likely where the error occurred.I will fix it as soon as possible. Also, please let me know which version has the issue,
Windows
,macOS
, orLinux
? Thank you.Windows 11, WindTerm_2.6.0_Windows_Portable_x86_64.zip
we are same environment
This issue has been fixed. Please download the latest version WindTerm 2.6.0 or WindTerm 2.7.0 Prerelease 1. I apologize for the delay in releasing the fixed version, as I have been traveling and working without reliable internet access.