ksharlaimov

This bug seems to be fixed in SyncApp version 1.0.92... I'll do more thorough testing tomorrow.

Update: The remote (HOMESERVER) log shows another strange entries: [20130304 16:50:43] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_bc14f4ab.jpg [20130304 16:50:43] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_be6d912a.jpg [20130304 16:50:43] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_c86fa434.jpg [20130304 16:50:44] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_cb740c2e.jpg [20130304 16:50:44] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_d157f198.jpg [20130304 16:50:44] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_d4de90c5.jpg [20130304 16:50:44] Going to connect to peer 94.25.124.150:11821 for file Images_final/24-ok/z_d5042b5c.jpg Strange thing is that these files are not present on either sides. Probably I've placed these files on WORKSTATION, then changed my mind and removed them before they were synced. Now SyncApp is stuck trying to replicate these not-existant files.

I have two peers sychronised by SyncApp. Today I ran into strange problem - I've moved a bunch of files on one peer (WORKSTATION, running Windows 7) and these files (some 507 Mb) are not replicated to HOMESERVER. However these 507 Mb are shown as pending (screenshot 1). Transfer tab shows some attempts to send files, but with no luck (screenshot 2). Debug logs on remote peer (HOMESERVER, running Ubuntu) once in a while shows strange entry: [20130304 15:26:23] SyncFilesController: Got 0 files from remote (94.25.124.150:11821), remote time is 1365049576, request delay: 1 There is NAT with manual port forwarding on both sides. I tried to restart both peers, checked network connectivity but no luck, those 507 Mb are still not replicated.

I've been tested Sync for a few days and migrated to it from DropBox. However, I have a suggestion to improve sync speed dramatically. Imagine the scenario: I have 2 nodes ("A" and "B") linked together by Sync. If I move a file within a shared folder on "A" without modifying it, Sync moves the file to "SyncTrash" from old location on "B" and re-syncs the very same file to its new location from "A" consuming time and bandwidth. It'd be nice if Sync maintained the list of files (and their infohashes) not only in shared folder itself but also in that folder's SyncTrash. By doing so Sync would be able to detect if the "known" file is going to be transfered from other peer, and restore it from it's local copy (with the same infohash) instead of copying it over the network again.