status update

diff --git a/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_15_85e2368381e15cd86b5340fcec1a083b._comment b/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_15_85e2368381e15cd86b5340fcec1a083b._comment
index 06c63dba9b4fd49a33e4b3b4a9d17c821b515ef9..2119af3724478f2dba10a9358387679405e1503e 100644 (file)
--- a/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_15_85e2368381e15cd86b5340fcec1a083b._comment
+++ b/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_15_85e2368381e15cd86b5340fcec1a083b._comment
@@ -26,5 +26,5 @@ transfer), otherwise the checksumming won't fall behind. It would be better
 to defer the rest of the incremental checksumming to the transfer stage
 (by returning the action inside Verification and running it when
 the verification is checked), or perhaps switch to the checksum stage
-before doing it.
+before doing it. (update: this is fixed)
 """]]

diff --git a/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_16_fbbcf1d8b35078274cfe322cea6de21c._comment b/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_16_fbbcf1d8b35078274cfe322cea6de21c._comment
index d24203b2b10c02d236008d420ab08649126bac3d..e5bc881d887652c2c788466bec40246536572f13 100644 (file)
--- a/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_16_fbbcf1d8b35078274cfe322cea6de21c._comment
+++ b/doc/todo/OPT__58_____34__bundle__34___get_+_check___40__of_checksum__41___in_a_single_operation/comment_16_fbbcf1d8b35078274cfe322cea6de21c._comment
@@ -14,15 +14,16 @@ sped it up. Seems that in Remote.Helper.Special, it uses
 RemoteVerify baser, but when shouldVerify checks that value, it
 sees that Types.Remote.isExportSupported is true. Despite the remote
 not actually being an export remote. Because adjustExportImport gets
-run after that point, I think..
+run after that point, I think.. (update: this is fixed)
 
 As well as the web special remote, these do not do incremental hashing
-still: gitlfs, S3. Problem is, these open the file
+still: gitlfs, S3, httpalso. Problem is, these open the file
 for write. That prevents tailVerify re-opening it for read, because the
 haskell RTS actually does not allowing opening a file for read that it has
 open for write. The new `fileRetriever\`` can be used instead to fix these,
-but will take some more work.
+but will take some more work. Also, the git remote, when accessing a
+repository over http does not do incremental hashing.
 
 Also, retrieval from export/import special remotes does not do incremental
-hashing.
+hashing (except for versioned ones, which sometimes use retrieveKeyFile).
 """]]