Automatic error handling in 2.3

[konics]

I recently downloaded v.2.3 and tried setting up the synchronization of my
folders as I did in v2.2, but I can't seem to get the automatic error handling
to work.
After doing some tests I've found that the program never ignores errors
although the settings clearly says it should. Instead when set to Ignore, the
program exits at the first error or warning.

Is this something you can replicate and perhaps fix?

It also seems like the error handling settings are completely ignored when not
running in Silent mode. If set to Exit with RC <0 the program still shows a
pop-up for any error. Is this intended behavior?

[Zenju]

Alright, error handling is somewhat complex, so here is the behaviour of a
batch run as it SHOULD be implemented:

silent mode:
-------------------
- ignore errors: ignores errors and warnings and continues
- exit with rc < 0: exits process immediately on errors or warnings
- show popup: shows a popup on each error or warning
- Additional rule: during comparison "ignore errors" is treated as "exit with rc < 0"

gui mode:
--------------
- ignore errors: ignores errors and warnings and continues
- exit with rc < 0: shows a popup on each error or warning
- show popup: shows a popup on each error or warning
- Additional rule: during comparison "ignore errors" is treated as "show popup"


------------
What's new in v2.3 are the "additional rules". So this should be
pretty much the behaviour you experience, right? The intention of the
"additional rules" is to prevent data loss, when for example a
remove drive is not accessible. In this case it's dangerous to continue,
because the (not reachable) drive is seen as empty, which is interpreted as a
deletion in one-way sync.
What are the errors you wish to "ignore" in your case?

Regards, Zenju

[konics]

I have Folder1 as the left folder and Folder2 as the right folder. Folder1 is
the "master" and Folder2 has to be exactly the same after a
synchronization. If Folder1 is emptied or has files removed, the same should
happen in Folder2.

There are times when Folder2 is deleted completely (if an unexpected error
occurred, it is standard procedure to remove Folder2). I would like for the
synchronization to consider Folder2 as empty and recreate it and it's sub-
folders.
The additional rule you describe would in my case treat Folder2 as not
accessible and then quit execution.

There is also a type of warning that will occur in my synchronization, which
is caused due to depending folders.
In Folder1 I have one file and one sub-folder, the sub-folder's contents
should go to another sub-folder under Folder2 and the file goes into another
sub-folder of Folder2.
The sync looks like this:

Folder1/File.dat -> Folder2/Filefolder/File.dat

Folder1/Datafolder -> Folder2/Datafolder

This also causes the program to exit execution, although the filters are
properly set up to never cause an issue.
There is of course a way around this problem using more batch files, but it
doesn't seem like a good solution when the program supports batch jobs with
separate filters now.

[Zenju]

It's hard to decide what is the best behaviour in this case: On the one hand
it might be that a source folder temporarily is not accessible by accident
which leads to a deletion in target folder, which is data loss!
On the other hand it this might be the INTENDED behaviour, because one
specified a not existing directory (or a blank string) as source in order to
delete target. Or, like in your case, target is not existing and you
implicitly want to create it during synchronization. The latter two scenarios
are no error situation.

--------------------
I've thought about all implications again and think it's best to be
transparent and clear: I'll remove both "Additional rules" again and
also remove "exit with rc < 0" for gui-mode.

Then the program will do EXACTLY what the user specified.
Additionally I'll add some information about option "ignore errors"
explaining the potential pitfall, if a directory is not existing.

[konics]

Thank you for the quick response, I look forward to your updated version of
the program.

I'd also like to point out that you did an excellent work with the optional
filters and rules for batch jobs in v.2.3, it's very easy to use and
understand.

Keep up the good work!

[srjones67]

Any time frame on this change?

[Zenju]

> Any time frame on this change?
It's already implemented. Next release will be beginning to mid of next week.

[srjones67]

As always, you have prompt response. Thank you again for a great product!

[Zenju]

> Additionally I'll add some information about option "ignore
errors"
> explaining the potential pitfall, if a directory is not existing.

I've found an even better solution with NO pitfail, EVEN if the user chose to
ignore errors: Roughly: If source directory doesnt exists and leads to
deletion of target, the sync is aborted. (If target directory doesn't exists
it's no problem, it's created implicitly, but issues an (ignorable) error
message... no change in behaviour here) ... that's nice so far. Even in the
(unlikely?) scenario where someone intentionally wants to delete target by
specifying an invalid source directory, he can do so, by explicitly leaving
source empty.

Win all, lose nothing! These are the kind of designs I like! ;)

[srjones67]

(If target directory doesn't exists it's no problem, it's created implicitly,
but issues an (ignorable) error message... no change in behavior here)
But right now even if I pick Ignore errors, when I run interactively or in batch it's not ignoring when the source exists but target doesn't. This causes trouble in unattended mode.

[Zenju]

>> But right now even if I pick Ignore errors
Yes, this was the "old" design. With the new version this problem
won't occur anymore.

[srjones67]

Is this new version the one that you mentioned would be out this week?

[Zenju]

Yes