Search the Community
Showing results for tags 'logging'.
I think a key missing feature from Sync is stopping errors from propagating by interacting with the user and presenting her with options on what one can do. As an example, I recently filed an issue #49958 where the indexing was out of control. It turned out that due to some naming conflict (probably due to the composed/decomposed issue) *.Conflict folders were being created. By the time we found out why indexing never finished 1.4 million such conflict folders had been created for one particular weirdly named folder. When stuff like that happens Sync should notify the user that something
Hi. I am using btsync (newest version, 1.3.106) on a few computers (windos 8, 64 bit), spreaded around germany and connected via VPN. I now realised, that the logging ("chronic" on GUI) doesn't show up the actual changes correctly. I don't know, if this is already in fixing but i didn't see a thread about this. Many changes are logged there, but some changes (adding new small txt-file to sync.folder or deleting some small files) aren't shown up there BUT they are still synced correctly. This happens not only on one computer, it happens on at least 2 and i think it will happen on every computer