rsync flags some files as failing to transfer even though the file was successfully transferred

[tieneupin]

These appear to be false positives due to the file path changing between when the file is first detected and after it's transferred. The file is present at the destination location even though the error was triggered. Will need to figure out what changed, and how the rsync module can be optimised to prevent this from occurring further.

[tieneupin]

Now that Pull Request #319 has gone live, it can be seen that the successful transfer message implemented under murfey.client.tui.app (line 235) has never been triggered, even though files are successfully being transferred.

This would indicate that the error lies in the condition set(relative_filenames) - transfer_success in murfey.client.rsync (line 440), which appears to be the only occurrence in the code base of Transfer_Result being set to FAILURE.