feat(parity): rsync-parity cycle 2.29 (120/10/27, no wire change) #305

Merged

TapTap merged 8 commits from feat/parity-2.29 into dev 2026-09-20 15:10:18 +02:00

Conversation 0 Commits 8 Files Changed 27

+2130 -440

8 Commits

Author	SHA1	Message	Date
TapTap	9b05972375	test: assert partial --max-delete survivor order matches rsync	2026-09-20 15:02:51 +02:00
TapTap	d119f35066	docs: record parity cycle 2.29 (120/10/27) and deferred residuals	2026-09-20 15:02:44 +02:00
TapTap	00829fd265	parity: --info=mount/stats, --stats dir breakdown, --debug categories ... --info=mount now prints rsync's mount-point skip line (matching rsync 3.4.1, which emits it for repeated -xx and drops the mount-point dir); --info=stats enables the same block as --stats; -x is repeatable. --stats counts traversed directories for the Number of files breakdown even when no directory metadata is captured (-r without -t/-p). --debug enables real output for flist/del/hash/deltasum/recv/filter/send at their natural FastSync events (synthetic categories stay inert). --stats and --debug rows keep their documented residual status.	2026-09-20 14:55:47 +02:00
TapTap	ff261bc38a	test: extend rsync order parity to dry-run and delete-delay	2026-09-20 14:55:47 +02:00
TapTap	b235721f8b	delete: rsync-exact abort boundary and -d per-directory plans ... Transmit the complete --delete-during/--delete-delay per-directory plan set before the first data frame, so a mid-transfer abort has already applied every planned removal like rsync's generator; completed runs are unchanged. Route -d/--dirs through the same per-directory plans: the generator records only directories whose direct children it enumerated, so extras directly inside a listed directory are removed while an untraversed subdirectory's mirror is shielded (rsync's -d DIR/ --delete). Also shields a -x mount point's untraversed destination content.	2026-09-20 14:22:22 +02:00
TapTap	79a28cdb96	scanner: emit entries in rsync's sorted depth-first flist order ... Buffer and sort each directory's inspected entries (non-directories ascending, then directories ascending) and walk them depth-first via a LIFO directory stack, so the sequential scanner's stream matches rsync 3.4.1's flist order. This makes the --info=name transfer order and the --delete-during/--delete-delay deletion sequence byte-identical to rsync (differential tests in test_parity_order.py); --threads stays unordered (no rsync analogue) and is documented as such. Adds LIFO queue_push/queue_pop over the existing ring buffer.	2026-09-20 13:49:04 +02:00
TapTap	402cae80ad	parity: rsync-exact relative basis-dir resolution and fuzzy eligibility ... Resolve a relative --compare-dest/--copy-dest/--link-dest DIR against the destination directory and append the file's transfer-relative name, as rsync 3.4.1 does, instead of appending FastSync's source-mirrored wire path (the historical spelling stays as a fallback for existing layouts). Stop inheriting the ordinary delta engine's 16 KiB minimum and 10x size ratio in the -y/--fuzzy candidate search: rsync's find_fuzzy has no delta-size gate, so an oversized or sub-16-KiB sibling is now reused. The ordinary delta path's bounds are unchanged.	2026-09-20 13:39:04 +02:00
TapTap	9691dba6f0	delete: reproduce rsync traversal order for extras removal ... Collect each directory's entries up front and process extraneous subdirectories first (descending name, depth-first), then extraneous files (descending name), then descend into kept subdirectories in ascending order. Emit a trailing slash for deleted directories in observers/dry-run output. This matches rsync's delete order for --delete-before/--delete-after/--delete-delay and for dry-run listings.	2026-09-20 13:15:04 +02:00