Skip to content

Accept comma-separated skip-compress patterns#1194

Merged
oferchen merged 1 commit into
masterfrom
implement-missing-components-for-oc-rsync
Oct 27, 2025
Merged

Accept comma-separated skip-compress patterns#1194
oferchen merged 1 commit into
masterfrom
implement-missing-components-for-oc-rsync

Conversation

@oferchen
Copy link
Copy Markdown
Owner

Summary

  • mirror upstream skip-compress parsing by treating both / and , as separators
  • extend the skip-compress unit tests to cover comma-delimited specifications

Testing

  • cargo test -p rsync-engine skip_compress

https://chatgpt.com/codex/tasks/task_e_68febf063d108323baba438398c825ad

@oferchen oferchen merged commit 86ff6bf into master Oct 27, 2025
@oferchen oferchen deleted the implement-missing-components-for-oc-rsync branch October 27, 2025 00:45
oferchen added a commit that referenced this pull request May 5, 2026
Design note for TODO #1193. Adds docs/design/protocol-fuzzing-harness.md
covering a behavioural differential fuzz harness that drives both
oc-rsync and upstream rsync 3.4.1 through randomized end-to-end
transfer scenarios and asserts equivalence on exit code, destination
tree bytes, wire payload (tcpdump), and stderr structure. Sister to
the wire-byte fuzz at crates/protocol/fuzz/ (#1194) and the wire-format
differential fuzzer at #1303.

Documents only. Zero impact on production code paths; the harness lives
in a new fuzz-harness crate outside the production dependency graph.
oferchen added a commit that referenced this pull request May 18, 2026
Design note for TODO #1193. Adds docs/design/protocol-fuzzing-harness.md
covering a behavioural differential fuzz harness that drives both
oc-rsync and upstream rsync 3.4.1 through randomized end-to-end
transfer scenarios and asserts equivalence on exit code, destination
tree bytes, wire payload (tcpdump), and stderr structure. Sister to
the wire-byte fuzz at crates/protocol/fuzz/ (#1194) and the wire-format
differential fuzzer at #1303.

Documents only. Zero impact on production code paths; the harness lives
in a new fuzz-harness crate outside the production dependency graph.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant