CRC implementation (packed Base64 encoded MD5) #2
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Currently missing files need to be manually deleted after the download process has finished. By utilizing the
md5
(24 character packed base64 encoded MD5) field the API provides, this could be streamlined. Besides file integrity checking this'd also be pretty useful for preventing duplicates.The only issue is that I haven't yet quite figured out what's wrong with the conversion implementation. E.g. the following example should produce the same packed representation as the API does, but that's not the case in practice: