Make parsed receiver and scanner options affect behavior or fail explicitly #206
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Severity
Medium
Description
Several advertised options are parsed/serialized but ignored or applied inconsistently: single-threaded receiver saves pass NULL config, deletion policy flags do not alter manifest deletion, --filter/--files-from/--relative/--cvs-exclude are not applied by the scanner, --links does not transmit symlink targets, and --queue-size is not threaded through all queues.
Location
Validation
Run equivalent transfers with and without -m using backup/inplace/sparse options; exercise deletion timing/max-delete; use files-from/filter/relative and links; configure a small queue size and inspect queue capacities.
Suggested implementation
Either implement each documented option end-to-end and test serial/parallel receivers, or reject unsupported combinations during CLI validation instead of silently reporting success.