TastyHeadphones 1d11d94927 bisync: fix internal error when a conflict rename reuses deleted names - fixes #10165 ...

If a file is changed on both sides and the conflict names it gets renamed
to (e.g. X.conflict1 and X.conflict2) were deleted on both sides since the
last run, the listing update removed the just-copied conflict files again
when processing the deleted-on-both queue. The rename bookkeeping then
could not find them and bisync aborted with "bisync.renames: internal
error: missing info".

Skip names that this run copied when removing files deleted on both sides,
and add a test case for the scenario.

2026-10-26 17:41:40 +00:00

..

test_all_changed

…

test_backupdir

…

test_basic

…

test_changes

…

test_check_access

…

test_check_access_filters

…

test_check_filename

…

test_check_sync

…

test_compare_all

…

test_concurrent

…

test_conflict_reuse

…

test_conflict_window

…

test_conflict_window_size

…

test_createemptysrcdirs

…

test_dry_run

…

test_equal

…

test_equal_skipped

…

test_ext_paths

…

test_extended_filenames

…

test_filters

…

test_filtersfile_checks

…

test_ignorelistingchecksum

…

test_max_delete_path1

…

test_max_delete_path2_force

…

test_max_delete_track_renames

…

test_nomodtime

…

test_normalization

…

test_rclone_args

…

test_resolve

…

test_resync

…

test_resync_modes

…

test_rmdirs

…

test_volatile

…