You are here

Possible Flaw in logic for File Checks?

2 posts / 0 new
Last post
Last seen: 13 years 10 months ago
Joined: 2010-09-13 10:37
Possible Flaw in logic for File Checks?

After running some tests to see if I wanted to switch over to Toucan. I think I've found a logical flaw causing a changed file to never be copied.

For example If I create a test Sync job with the settings
File Checks->File Size, Modified Time, and Short Comparison

Ok now lets say I just want to sync one file test.txt whose contents are:
this is a test file.

Now upon first run this copies the file since it is not present on the destination. Good works there.

Next I change test.txt contents to: (Note the capitalization of the t)
This is a test file.

Now when I run this, it does not copy the file since the file size is the same, even though the Modified Time is different, and the Short Comparison is different.

It seems that the internal logic is OR'd rather than AND'd. Am I missing something? Shouldn't it try each test until False? and not until True?
For instance.
File Size is the same, keep going.
Modified Time is the different, copy the file.


Steve Lamerton
Steve Lamerton's picture
Last seen: 10 years 10 months ago
Joined: 2005-12-10 15:22

are indeed correct, this should already be fixed in the latest pre-release which you can find here. Thanks for the report Smile

Log in or register to post comments