From 41ef54276ba65f23690e78728dcb0537728d7023 Mon Sep 17 00:00:00 2001 From: anarcat Date: Mon, 17 Jun 2019 20:17:27 +0000 Subject: [PATCH 1/5] Added a comment: thanks! --- .../comment_1_334c36d503abd06611a46cc102139446._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/devblog/day_594__finally_background_checksum_verification/comment_1_334c36d503abd06611a46cc102139446._comment diff --git a/doc/devblog/day_594__finally_background_checksum_verification/comment_1_334c36d503abd06611a46cc102139446._comment b/doc/devblog/day_594__finally_background_checksum_verification/comment_1_334c36d503abd06611a46cc102139446._comment new file mode 100644 index 0000000000..4770ea6aa1 --- /dev/null +++ b/doc/devblog/day_594__finally_background_checksum_verification/comment_1_334c36d503abd06611a46cc102139446._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="anarcat" + avatar="http://cdn.libravatar.org/avatar/4ad594c1e13211c1ad9edb81ce5110b7" + subject="thanks!" + date="2019-06-17T20:17:26Z" + content=""" +thanks so much for this work! it's something I had identified as an annoyance in the conversation around [[forum/does_git-annex_parallelize_different_remotes__63__]] and I'm really happy to see you're working on this! so yeah, thanks again! :) +"""]] From ce7b9ecae6651dfac8b6e6a823622905c0c47858 Mon Sep 17 00:00:00 2001 From: kyle Date: Mon, 17 Jun 2019 21:11:14 +0000 Subject: [PATCH 2/5] Added a comment: Issue with description cache? --- ..._c51d386f294529d6ebe7058438577ffe._comment | 36 +++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 doc/bugs/annex_init_no_longer_generates_default_description/comment_2_c51d386f294529d6ebe7058438577ffe._comment diff --git a/doc/bugs/annex_init_no_longer_generates_default_description/comment_2_c51d386f294529d6ebe7058438577ffe._comment b/doc/bugs/annex_init_no_longer_generates_default_description/comment_2_c51d386f294529d6ebe7058438577ffe._comment new file mode 100644 index 0000000000..6459b7e103 --- /dev/null +++ b/doc/bugs/annex_init_no_longer_generates_default_description/comment_2_c51d386f294529d6ebe7058438577ffe._comment @@ -0,0 +1,36 @@ +[[!comment format=mdwn + username="kyle" + avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3" + subject="Issue with description cache?" + date="2019-06-17T21:11:14Z" + content=""" +I took another look at this thinking that maybe I could spot something obvious in the condition added in a14f6ce75 + +``` + {- Avoid overwriting existing description with a default + - description. -} + whenM (pure (isJust mdescription) <||> not . M.member u <$> uuidDescMap) $ + describeUUID u =<< genDescription mdescription +``` + +but that looks fine. Grepping around for uuidDescMap, I spotted a couple of places where the cache needed to be invalidated. Blindly applying that same approach I did + +``` +diff --git a/Annex/Init.hs b/Annex/Init.hs +index cb7f8905e..6303103df 100644 +--- a/Annex/Init.hs ++++ b/Annex/Init.hs +@@ -76,6 +76,7 @@ genDescription Nothing = do + + initialize :: Maybe String -> Maybe RepoVersion -> Annex () + initialize mdescription mversion = checkCanInitialize $ do ++ uuidDescMapLoad + {- Has to come before any commits are made as the shared + - clone heuristic expects no local objects. -} + sharedclone <- checkSharedClone +``` + +That fixes the problem on my end (i.e., `git annex init` sets the description to the default user@host:dir description) while still addressing the original issue fixed by a14f6ce75. + +So it seems like it has something to do with the uuidDescMap cache, but I haven't been able to figure out what in particular. +"""]] From 03c7e06c2b17be95b65b50b103b01e86be9b35cb Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Tue, 18 Jun 2019 19:56:21 +0000 Subject: [PATCH 3/5] added forum question about git-annex-sync errors with bitbucket.org --- doc/forum/git-annex-sync_with_bitbucket.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) create mode 100644 doc/forum/git-annex-sync_with_bitbucket.mdwn diff --git a/doc/forum/git-annex-sync_with_bitbucket.mdwn b/doc/forum/git-annex-sync_with_bitbucket.mdwn new file mode 100644 index 0000000000..2c1526ef9f --- /dev/null +++ b/doc/forum/git-annex-sync_with_bitbucket.mdwn @@ -0,0 +1,11 @@ +When doing `git-annex-sync` with a [Bitbucket](https://bitbucket.org) repository, I get the errors: + +>(master_env_v17) /web/personal/ilya > git annex sync +> +>Failed to get annex.uuid configuration of repository origin +> +>Instead, got: "logged in as notestaff\n\nYou can use git or hg to connect to Bitbucket. Shell access is disabled\n" +> +>This is unexpected; please check the network transport! + +What is the right way to fix this? Thanks! From 247bc2133169309148d5037072f081e43be33022 Mon Sep 17 00:00:00 2001 From: kyle Date: Wed, 19 Jun 2019 14:18:20 +0000 Subject: [PATCH 4/5] Added a comment: Set remote..annex-ignore --- .../comment_1_b95e03d119c83ac061c470801b157d55._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/git-annex-sync_with_bitbucket/comment_1_b95e03d119c83ac061c470801b157d55._comment diff --git a/doc/forum/git-annex-sync_with_bitbucket/comment_1_b95e03d119c83ac061c470801b157d55._comment b/doc/forum/git-annex-sync_with_bitbucket/comment_1_b95e03d119c83ac061c470801b157d55._comment new file mode 100644 index 0000000000..19e092d8ea --- /dev/null +++ b/doc/forum/git-annex-sync_with_bitbucket/comment_1_b95e03d119c83ac061c470801b157d55._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="kyle" + avatar="http://cdn.libravatar.org/avatar/7d6e85cde1422ad60607c87fa87c63f3" + subject="Set remote..annex-ignore" + date="2019-06-19T14:18:19Z" + content=""" +I think in this case you should set remote.origin.annex-ignore to true. +"""]] From 3a19ef7994d5c2b98ac5e17c5e384416fc73abee Mon Sep 17 00:00:00 2001 From: Ilya_Shlyakhter Date: Wed, 19 Jun 2019 16:51:31 +0000 Subject: [PATCH 5/5] Added a comment --- .../comment_2_31f7eae218447a17f316a8d13dd97ca0._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/git-annex-sync_with_bitbucket/comment_2_31f7eae218447a17f316a8d13dd97ca0._comment diff --git a/doc/forum/git-annex-sync_with_bitbucket/comment_2_31f7eae218447a17f316a8d13dd97ca0._comment b/doc/forum/git-annex-sync_with_bitbucket/comment_2_31f7eae218447a17f316a8d13dd97ca0._comment new file mode 100644 index 0000000000..f16c97f2a9 --- /dev/null +++ b/doc/forum/git-annex-sync_with_bitbucket/comment_2_31f7eae218447a17f316a8d13dd97ca0._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="Ilya_Shlyakhter" + avatar="http://cdn.libravatar.org/avatar/1647044369aa7747829c38b9dcc84df0" + subject="comment 2" + date="2019-06-19T16:51:31Z" + content=""" +But I do want git-annex-sync to sync the git-annex branch with that remote. +Normally, git-annex deals with the case of git remotes that don't support git-annex-shell without giving an error. +"""]]