fix windows transfer lock check
If the lock file was not able to be exclusivlely locked, don't indicate
locking failed. I'm pretty sure this was a typo. It goes all the way
back to 891c85cd88
where locking was first
introduced on windows, and there's no indication of why it would make
sense to return True here.
Sponsored-by: Leon Schuermann on Patreon
This commit is contained in:
parent
1ace305159
commit
62129f0b24
1 changed files with 1 additions and 1 deletions
|
@ -171,7 +171,7 @@ runTransfer' ignorelock t eventualbackend afile stalldetection retrydecider tran
|
|||
createAnnexDirectory $ P.takeDirectory lck
|
||||
catchMaybeIO (liftIO $ lockExclusive lck) >>= \case
|
||||
Nothing -> return (Nothing, False)
|
||||
Just Nothing -> return (Nothing, True)
|
||||
Just Nothing -> return (Nothing, False)
|
||||
Just (Just lockhandle) -> do
|
||||
createtfile
|
||||
return (Just lockhandle, False)
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue