From be581a2722e78f8a2e59e5ca78a1090efc432307 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 27 Oct 2013 16:42:13 -0400 Subject: automatically launch git repository repair Added a RemoteChecker thread, that waits for problems to be reported with remotes, and checks if their git repository is in need of repair. Currently, only failures to sync with the remote cause a problem to be reported. This seems enough, but we'll see. Plugging in a removable drive with a repository on it that is corrupted does automatically repair the repository, as long as the corruption causes git push or git pull to fail. Some types of corruption do not, eg missing/corrupt objects for blobs that git push doesn't need to look at. So, this is not really a replacement for scheduled git repository fscking. But it does make the assistant more robust. This commit is sponsored by Fernando Jimenez. --- Remote.hs | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) (limited to 'Remote.hs') diff --git a/Remote.hs b/Remote.hs index a7f0975c5..71db09ce7 100644 --- a/Remote.hs +++ b/Remote.hs @@ -39,7 +39,8 @@ module Remote ( showTriedRemotes, showLocations, forceTrust, - logStatus + logStatus, + checkAvailable ) where import qualified Data.Map as M @@ -274,3 +275,7 @@ byCost = map snd . sortBy (comparing fst) . M.toList . costmap where costmap = M.fromListWith (++) . map costpair costpair r = (cost r, [r]) + +checkAvailable :: Bool -> Remote -> IO Bool +checkAvailable assumenetworkavailable = + maybe (return assumenetworkavailable) doesDirectoryExist . localpath -- cgit v1.2.3