Allow User to Force Upload During Check-in

[carl_martinQ36PJ]

Vault uses the CRC32 checksum to detect changes in files which has 4,294,967,296 possible values.  This seems like a huge number, but when you consider a system with a million files each with 10 or more versions, the probability of a CRC32 clash becomes highly probable.  In addition, some softwares have been known to abuse the CRC32 checksum resulting in frequent duplication.

Currently, when Vault recognizes that the checksum hasn't changed during the check-in process, it cancels the upload without warning to the user.  I'd like to suggest that the user instead be prompted with a dialog box that warns the user that the file queued for upload has the same checksum as the existing file in the Vault.  This dialog box would give the user the ability to force an upload if desired.

Alternatively, Vault's algorithm could consider the CRC64 instead of the CRC32 or consider both.  The CRC64 has 1.8 quintillion possible values.

[joshua_powell4GE6G]

100% back this, while the most common target for this error is items like .mer which don't change CRC32 upon change, it is the under the table dropping of this "unchanged" file rather than prompting the user if they wish to discard the unchanged version which ultimately should be adjusted. While from some perspectives this hidden function saves versions and disk space consumption, the hidden nature of it can lead to unintended data loss with the .mer file format being a key example without any knowledge of the fact until the dataloss if found and downstream impact already realised from this loss.

[ihayesjr]

@carl_martinQ36PJ What file type are you having this problem with?
My first thought is that this will be an annoying prompt because it will happen whenever too many files are checked out, and many of them haven't changed. Then the user will, by default, just say "Yes" and check in files unnecessarily, causing the environment to grow faster.