Skip to content

Verify target file exists after sync writes#56

Merged
pixelate merged 1 commit into
mainfrom
claude/verify-target-file-written
Apr 25, 2026
Merged

Verify target file exists after sync writes#56
pixelate merged 1 commit into
mainfrom
claude/verify-target-file-written

Conversation

@pixelate
Copy link
Copy Markdown
Owner

@pixelate pixelate commented Apr 22, 2026

Summary

  • Add Scanner#verify_written to log an error when the target file is missing after an acid-chunk write, copy, or conversion.
  • Catches silent failures from MTP/FUSE-mounted devices (e.g. TP-7) where invalid filename characters cause the transfer to be dropped without surfacing an error to userspace.

Test plan

  • bundle exec rake test TEST=test/wavesync/scanner_test.rb
  • Run a real sync to a TP-7 with a filename containing FAT-reserved characters (?, :) and confirm a Scanner#verify_written entry lands in wavesync.log.

@pixelate pixelate force-pushed the claude/wavesync-crystal-evaluation-A07eM branch from 736d767 to f2c5a16 Compare April 24, 2026 17:59
Log an error when the target file is missing after an acid-chunk
write, copy, or conversion. Catches silent failures from MTP/FUSE
mounts that accept writes without surfacing errors.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@pixelate pixelate force-pushed the claude/verify-target-file-written branch from 334facc to 2c6fbf8 Compare April 25, 2026 08:50
@pixelate pixelate changed the base branch from claude/wavesync-crystal-evaluation-A07eM to main April 25, 2026 08:51
@pixelate pixelate merged commit 29d8503 into main Apr 25, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant