status update
This commit is contained in:
parent
d67da1f4db
commit
1dca3ba26a
2 changed files with 6 additions and 5 deletions
|
@ -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)
|
||||
"""]]
|
||||
|
|
|
@ -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).
|
||||
"""]]
|
||||
|
|
Loading…
Add table
Reference in a new issue