nielash 6d6dc00abb bisync: rollback listing on error ... Before this change, bisync had no mechanism for "retrying" a file again next time, in the event of an unexpected and possibly temporary error. After this change, bisync is now essentially able to mark a file as needing to be rechecked next time. Bisync does this by keeping one prior listing on hand at all times. In a low-confidence situation, bisync can revert a given file row back to its state at the end of the last known successful sync, ensuring that any subsequent changes will be re-noticed on the next run. This can potentially be helpful for a dynamically changing file system, where files may be changing quickly while bisync is working with them.		2024-01-20 14:50:08 -05:00
..
_testdir_path1.._testdir_path2.copy1to2.que	bisync: test scenarios #5164	2021-11-01 21:00:27 +03:00
_testdir_path1.._testdir_path2.copy2to1.que	bisync: test scenarios #5164	2021-11-01 21:00:27 +03:00
_testdir_path1.._testdir_path2.path1.lst	bisync: rollback listing on error	2024-01-20 14:50:08 -05:00
_testdir_path1.._testdir_path2.path1.lst-new	bisync: rollback listing on error	2024-01-20 14:50:08 -05:00
_testdir_path1.._testdir_path2.path1.lst-old	bisync: rollback listing on error	2024-01-20 14:50:08 -05:00
_testdir_path1.._testdir_path2.path2.lst	bisync: rollback listing on error	2024-01-20 14:50:08 -05:00
_testdir_path1.._testdir_path2.path2.lst-new	bisync: rollback listing on error	2024-01-20 14:50:08 -05:00
_testdir_path1.._testdir_path2.path2.lst-old	bisync: rollback listing on error	2024-01-20 14:50:08 -05:00
test.log	bisync: test scenarios #5164	2021-11-01 21:00:27 +03:00