diff hgext/lfs/wrapper.py @ 35553:a77418095530

lfs: remove the verification option when writing to the local store This partially reverts 417e8e040102 and bb6a80fc969a. But since there's now a dedicated download function, there's no functional change. The last sentence in the commit message of the latter is wrong- write() didn't need the one time hash check if verification wasn't requested. I suspect I missed 'read()' in there ("... but _read()_ also needs to do a one time check..."), because that did fail without the hash check before linking to the usercache. The write() method simply took the same check for consistency. While here, clarify that the write() method is *only* for storing content directly from filelog, which has already checked the hash. If someone can come up with a way to bridge the differences between writing to a file and sending a urlreq.request across the wire, we can create an upload() function and cleanup read() in a similar way. About the only common thread I see is an open() that verifies the content before returning a file descriptor.
author Matt Harbison <matt_harbison@yahoo.com>
date Sun, 07 Jan 2018 01:14:52 -0500
parents fa865878a849
children ebf14075a5c1
line wrap: on
line diff
--- a/hgext/lfs/wrapper.py	Thu Dec 21 21:20:00 2017 -0500
+++ b/hgext/lfs/wrapper.py	Sun Jan 07 01:14:52 2018 -0500
@@ -86,7 +86,7 @@
 
     # git-lfs only supports sha256
     oid = hashlib.sha256(text).hexdigest()
-    self.opener.lfslocalblobstore.write(oid, text, verify=False)
+    self.opener.lfslocalblobstore.write(oid, text)
 
     # replace contents with metadata
     longoid = 'sha256:%s' % oid