Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide option to expand threshold for reading whole file into CRC32 hash #14

Open
agirardeau opened this issue Jul 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@agirardeau
Copy link

agirardeau commented Jul 11, 2024

When calculating a file hash, files that are <= 16KiB are read in their entirety into a CRC32 fingerprint, while files > 16KiB have only their "crucial bytes" read, as explained in #1 (comment). I work with some files that are in the 50-100KiB range, and are particularly likely to have edits that don't change the file size or affect the critical bytes (they're kinda like csv but with space-padded cells, similar to markdown or org-mode tables). It would be great to just bump up the threshold for fingerprinting the whole file to like 200KiB. I'm using rsync-sidekick for archive so safety is more important than performance. Would it be possible to add an option for this?

@m-manu m-manu self-assigned this Jul 27, 2024
@m-manu m-manu added the enhancement New feature or request label Jul 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants