From 67524c3a41a2c0b5e8c34bcbfde737ca50fc191b Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 11 Apr 2013 17:15:45 -0400 Subject: connect existing meters to the transfer log for downloads Most remotes have meters in their implementations of retrieveKeyFile already. Simply hooking these up to the transfer log makes that information available. Easy peasy. This is particularly valuable information for encrypted remotes, which otherwise bypass the assistant's polling of temp files, and so don't have good progress bars yet. Still some work to do here (see progressbars.mdwn changes), but this is entirely an improvement from the lack of progress bars for encrypted downloads. --- Command/TransferKey.hs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'Command/TransferKey.hs') diff --git a/Command/TransferKey.hs b/Command/TransferKey.hs index eb657d738..13790dd50 100644 --- a/Command/TransferKey.hs +++ b/Command/TransferKey.hs @@ -52,8 +52,8 @@ toPerform remote key file = go $ fromPerform :: Remote -> Key -> AssociatedFile -> CommandPerform fromPerform remote key file = go $ - download (uuid remote) key file forwardRetry $ - getViaTmp key $ Remote.retrieveKeyFile remote key file + download (uuid remote) key file forwardRetry $ \p -> + getViaTmp key $ \t -> Remote.retrieveKeyFile remote key file t p go :: Annex Bool -> CommandPerform go a = ifM a ( liftIO exitSuccess, liftIO exitFailure) -- cgit v1.2.3