6 Commits

Include renames

Author	SHA1	Message	Date
TapTap	36d4d0e43e	feat(parity): wire-stats protocol 2.25.0 + out-format %b/%c/%C ... Bump PROTOCOL_VERSION to 2.25.0 and append a report_stats bool to the config frame, add a STATUS_STATS status, and add process-wide wire byte counters (protocol_bytes_written/read) for the client. Render the rsync 3.4.1 --out-format %b (wire bytes sent) and %c (wire bytes read back) tokens from per-file counter deltas, and %C (whole-file xxh128 checksum, seed 0) via a new streaming checksum_digest_file().	2026-09-16 22:35:43 +02:00
TapTap	82a1d5e240	fix(delete): match rsync deletion semantics (#290) ... - Scope the --delete extras walk to directories synchronized by the transfer: add a synchronized-directory section to the delete manifest (protocol 2.23.0) so --files-from subsets no longer delete untransmitted paths outside listed directory subtrees (data-loss fix). - Separate --max-size/--min-size prune protection from --delete-excluded so size-pruned source mirrors survive (rsync parity). - Unlink extraneous destination symlinks instead of skipping them. - Make --max-delete partial (delete up to N, skip the rest) and exit 25; accept negative values as unlimited. - Draw --delete-missing-args deletions from the shared --max-delete budget. - Honor --force during --delay-updates publication. Add unit and integration regression tests; update the pinned config wire golden and version strings for the 2.23.0 manifest/status additions.	2026-09-15 23:12:03 +02:00
TapTap	93c1fc3c1f	test: create fault-injection destination root in seeding fixture ... The captured_config fixture assumed fault_dst already existed, relying on earlier tests in the same xdist worker creating it via _recover. Under --dist=load a worker can receive the capture test first, so the receiver rejected a missing destination root and the capture run failed. Create DEST_DIR in the autouse seeding fixture so test order/distribution cannot matter.	2026-09-15 20:02:00 +02:00
TapTap	34970b961c	feat: per-attribute preservation flags -p/-t/-o/-g with --no-* negations (protocol 2.22.0) ... Split FastSync's single use_metadata bundle into four independent rsync-parity attributes: preserve_perms, preserve_times, preserve_owner, preserve_group. use_metadata is now a derived transport bit (config_derived_use_metadata). CLI: real -p/--perms, -t/--times, -o/--owner, -g/--group plus --no-perms/--no-times/--no-owner/--no-group (short and long) and --no-preserve; -a is now rsync -rlptgoD; --preserve = -pt; -A implies -p; -X does not; --chmod implies -p; --usermap/--groupmap/--chown imply owner/group per side; --incremental/--delta still auto-preserve unless negated. Receiver: per-attribute FileAttrPolicy gating for files, dirs (modes applied at end of transfer), symlinks and specials; rsync -E read-bit rule; new files get source_mode & ~umask sanitized (no group/other write); per-side identity resolution; deferred directory metadata; batch dir-metadata replay; daemon modules without 'client owner = yes' no longer refuse plain -a but force super off (no ownership) with a warning. Wire: PROTOCOL_VERSION 2.21.0 -> 2.22.0 (four appended config bools, golden 653 / 95530566005420798). FileMetadata/chunk/batch framing unchanged. Docs/CHANGELOG/CMake updated to 2.22.0.	2026-09-15 19:32:02 +02:00
TapTap	88aee6ce94	feat(protocol): add optional STATUS_ERROR_DETAIL rejection reason (2.21.0) ... Today a server rejection sends a bare STATUS_ERROR and the reason only reaches the server log, so the client cannot say why a transfer was refused. Add an optional, bounded server->client error-detail frame: - Status gains STATUS_ERROR_DETAIL appended LAST so existing wire values are unchanged. - send_error_detail(fd, msg) sends STATUS_ERROR_DETAIL followed by the existing length-prefixed string primitive, slicing over-long messages to MAX_ERROR_DETAIL_BYTES (4096). - receive_status() (and the timed/keepalive status readers) always consume the detail body and map the status back to STATUS_ERROR, capturing the text into a thread-local buffer exposed by protocol_last_error(); a bare STATUS_ERROR leaves it cleared. Every existing call site keeps working and the stream cannot desync. - Upgrade the daemon module gate / config validation (config.c), the final transfer failure (server.c) and receiver-side path/node validation (file_receive.c) to send a concrete reason; surface it on the client in client_send.c/config.c. - Bump PROTOCOL_VERSION to 2.21.0 (CMake VERSION, CHANGELOG, docs) and update the pinned config wire golden hash / CLI-version tests. - Add tests/test_protocol_error.c covering mapping+capture, the over-long bound, bare-error clearing, and thread-locality.	2026-09-13 12:19:46 +02:00
TapTap	2854a9d149	test: fuzz manifest/protocol/xattr, hardlink unit, fault injection	2026-09-13 06:24:46 +02:00