Skip to content

Fix quick-check skip logic for ignore-times parity#2064

Merged
oferchen merged 1 commit into
masterfrom
decompose-source-files-over-500-lines
Nov 8, 2025
Merged

Fix quick-check skip logic for ignore-times parity#2064
oferchen merged 1 commit into
masterfrom
decompose-source-files-over-500-lines

Conversation

@oferchen
Copy link
Copy Markdown
Owner

@oferchen oferchen commented Nov 8, 2025

Summary

  • align the local quick-check path with upstream by trusting size and timestamp matches when no checksum is requested
  • drop the now-unused content comparison helper that previously backed the extra scan

Testing

  • cargo test --package oc-rsync-cli transfer_request_with_ignore_times_forces_copy_despite_matching_timestamps -- --nocapture

Codex Task

@oferchen oferchen merged commit 635e95c into master Nov 8, 2025
@oferchen oferchen deleted the decompose-source-files-over-500-lines branch November 8, 2025 12:48
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines 115 to 118
return false;
}

if modify_window.is_zero() {
return files_content_equal(source_path, destination_path).unwrap_or(false);
}

true
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regress quick‑check accuracy when modify_window is zero

After removing the content comparison for zero modify_window, should_skip_copy now returns true whenever size and timestamp match, even if file contents differ. This means a local copy will leave stale data when a file is edited without changing its mtime (a case previously covered by should_skip_copy_detects_content_changes_with_identical_timestamps). The earlier files_content_equal check avoided this false skip; without it the copy logic no longer verifies the data and breaks the existing test’s expectation.

Useful? React with 👍 / 👎.

oferchen added a commit that referenced this pull request May 7, 2026
…#3933)

Document the four wire-compatible zsync-inspired matching speedups
(bithash prefilter #2059-2062, seq-match extend-run #2064-2066,
matched-block pruning #2068-2070, compact-keys layout #2072-2073)
with CHANGELOG snippets, a release notes block, an anti-spec
forbidding wire-feature advertisement, and a placeholder for
benchmark numbers pending #2081 and #2082.
oferchen added a commit that referenced this pull request May 18, 2026
…#3933)

Document the four wire-compatible zsync-inspired matching speedups
(bithash prefilter #2059-2062, seq-match extend-run #2064-2066,
matched-block pruning #2068-2070, compact-keys layout #2072-2073)
with CHANGELOG snippets, a release notes block, an anti-spec
forbidding wire-feature advertisement, and a placeholder for
benchmark numbers pending #2081 and #2082.
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