summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar openmedi <openmedi@web>2016-05-09 11:46:45 +0000
committerGravatar admin <admin@branchable.com>2016-05-09 11:46:45 +0000
commit8f7399bd1a5e0fbc2557e2fa2b0353183dc70c51 (patch)
tree7befc3133f65a196a7bfbcd524deb6733bf6d09f
parent2cc4c577616d8f8561e2a8fe8b0c54ed6b2aa72c (diff)
-rw-r--r--doc/forum/How_to_find_out_if_assitant_is_still_repairing__63__.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/How_to_find_out_if_assitant_is_still_repairing__63__.mdwn b/doc/forum/How_to_find_out_if_assitant_is_still_repairing__63__.mdwn
new file mode 100644
index 000000000..a95942434
--- /dev/null
+++ b/doc/forum/How_to_find_out_if_assitant_is_still_repairing__63__.mdwn
@@ -0,0 +1 @@
+I have a corrupted repository, that git annex assistant wanted to repair. Before clicing on the button to start the repairing process, I had to deactivate my internet connection for another reason. The daemon.log is showing some connection errors to my remotes. But since pressing the button to repair my repo, the webapp is not showing the dashboard and there's no indicator that's trustworthy enough, that stuff is happening. There are some git and git annex processes running, but is there really now better way to know, if the repairing process is making progress, or if I need to restart the assistant because I needed to reset my internet connection.