RsyncUI version release notes and changelogs.
Version 2.9.0
Version 2.9.0 - Jan 16, 2026 in development
The development of the next version has commenced. Currently, several enhancements have been implemented in this version. The version is scheduled for release by the end of January. It is likely that more updates will be committed in the future.
- In the Tasks menu, when using a single table for tasks, the “Use two tables Inspector” setting is disabled. Consequently, the Inspectors for Edit and Parameters are not closed when the tab is changed. Screenshots are provided below for reference.
- If the Parameters include the two parameters
--itemize-changesand--update, the output from rsync is enhanced. Please note that these parameters will increase the output from rsync. For more information, refer to the blog post titled “Verify remote”.
For further details, please refer to the following documents:
- a detailed Changelog
- a Code Quality Report
Version 2.8.7
Version 2.8.7 - Jan 14, 2026
It appears that the updated package successfully addresses the issue of missing statistics. I have not encountered the “no stats” problem after the update, and several users have downloaded the release candidate. The release candidate has been promoted to the official release.
In contrast to version 2.8.6, this release introduces only two updates: an updated package RsyncProcessStreaming and a function in package ParseRsyncOutput that writes debug data to a text file if the “no stats” issue occurs.
Additionally, there is a fixed issue with the command strings for Copy public SSH Key and Verify Public SSH Key within the “Verify Tasks” menu. The issue is that the displayed command incorrectly added the keygen command in front of the actual command.
For additional information regarding RsyncUI’s Swift Packages, kindly refer to the accompanying document.
Rsync Verify
In the coming days, I will release a release candidate for the new application, RsyncVerify. This application replaces the functionality that was removed from RsyncUI. You can read about the application in the blog post titled “Verify remote.” The application includes parsing and tagging of each line of output. It is important to note that RsyncVerify is not a replacement for RsyncUI. The motivation for developing RsyncVerify is outlined in the blog post.
Version 2.8.6
Version 2.8.6 - Jan 9, 2026
This release is a maintenance update. The previous release candidate has been upgraded to the new release.
There are a few UI updates.
The Verify remote functionality has been removed and will be integrated into its own standalone application. This change will enhance RsyncUI’s focus on its core functionality: data synchronization.
For further details, please refer to the following documents:
- a detailed Changelog
- a Code Quality Report
The “missing stats alert” continues to occasionally appear. The data synchronization is complete, but RsyncUI is reporting missing summary data. The package responsible for controlling the rsync process has been updated in development to resolve this issue. While I am aware of the cause, finding a solution that does not require setting a dedicated wait time appears to be challenging. However, I am actively working on this matter. The solution is scheduled to be released in the next version, 2.8.7, which is expected in late January 2026.
Additionally (in development), I have incorporated debug data writing within the package that processes the output from rsync. Whenever the “no stats” error is encountered, the package writes the complete output to storage for further investigation.
The package for the process object has been updated to ensure that all data is drained before the object is released. I am currently using it and it appears to be promising. A release candidate will be available in a few days. For more information about the package, please refer to the provided link.
The debug data when error
Upon incorporating debug data into the package responsible for processing the output generated by rsync, I successfully obtained the initial debug message in the test environment. Please refer to the following information, which elucidates the cause of the error encountered by RsyncUI and the expected output.
An error was encountered with this output. The output is missing after the line File list size:. The complete and expected output is provided below, there are six lines missing. Therefore, my assumptions are correct. Now, I need to determine how to delay the termination until all data has been read.
rsyncuidocs/.git/objects/e5/5d0b0156cfe35b9a3759bc708f46ca6383a08a
rsyncuidocs/.git/objects/e5/f2358069749eab3508ca3b65c05d434d147a88
deleting rsyncuidocs/content/en/blog/Version284.md
rsyncuidocs/.git/objects/f9/649c9b801b80bdb6f1c544b52bfc7ca90773c7
rsyncuidocs/.git/objects/fa/6ecc4f9f3638a30bb2b56a31b01fc31cc244f6
rsyncuidocs/.git/refs/heads/main
rsyncuidocs/.git/refs/remotes/origin/HEAD
rsyncuidocs/.git/refs/remotes/origin/main
rsyncuidocs/content/en/blog/Verifyremote.md
rsyncuidocs/content/en/blog/Version286.md
rsyncuidocs/content/en/docs/advanced/Verify.md
Number of files: 34,463 (reg: 28,218, dir: 6,201, link: 44)
Number of created files: 285 (reg: 262, dir: 23)
Number of deleted files: 26 (reg: 24, dir: 2)
Number of regular files transferred: 375
Total file size: 2,578,503,779 bytes
Total transferred file size: 4,537,894 bytes
Literal data: 4,537,894 bytes
Matched data: 0 bytes
File list size: 280,193
This is what the trailing output should be:
Number of files: 34,463 (reg: 28,218, dir: 6,201, link: 44)
Number of created files: 0
Number of deleted files: 0
Number of regular files transferred: 1
Total file size: 2,578,505,001 bytes
Total transferred file size: 3,957 bytes
Literal data: 0 bytes
Matched data: 0 bytes
File list size: 24,576 <-- "This is were the above trailing ouput is cut off and causing an error"
File list generation time: 0.002 seconds
File list transfer time: 0.000 seconds
Total bytes sent: 1,261,175
Total bytes received: 6,764
sent 1,261,175 bytes received 6,764 bytes 845,292.67 bytes/sec
total size is 2,578,505,001 speedup is 2,033.62 (DRY RUN)
Empty stats file (no stats)
The process termination signal indicates that the external rsync process has completed and terminated. All tasks within the main synchronize view are updated with the latest run, but there is also separate logging that records the main result of each task with a timestamp.
Occasionally, when synchronizing a small amount of data, the termination signal is detected before all output from rsync has been read. In such cases, the separate logging may be incomplete. The process termination signal serves as a trigger to perform logging, but if the last summarized rsync output is missing, there is nothing to log.
Output from rsync refers to the information that rsync provides to the terminal during the execution of a task.
If RsyncUI detects an empty statistics file, it will append a default log record stating 0 files : 0.00 MB in 0.00 seconds.
If logging fails due to the aforementioned reason, this error will be generated, if enabled.
