From f0b5fce5ab2eb2ce5992bd2f11731afebb98330d Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 23 Jan 2025 15:53:39 +0000 Subject: [PATCH 1/4] Added a comment --- ...comment_1_704469f0deb075d0b3c70c73708cd456._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/git-annex-dead/comment_1_704469f0deb075d0b3c70c73708cd456._comment diff --git a/doc/git-annex-dead/comment_1_704469f0deb075d0b3c70c73708cd456._comment b/doc/git-annex-dead/comment_1_704469f0deb075d0b3c70c73708cd456._comment new file mode 100644 index 0000000000..11cd23cf15 --- /dev/null +++ b/doc/git-annex-dead/comment_1_704469f0deb075d0b3c70c73708cd456._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 1" + date="2025-01-23T15:53:39Z" + content=""" +is there `git annex undead` to easily mitigate users doing what they should have not done? ;-) + +Would it be sufficient to just remove the corresponding `X` line from `trust.log`? +"""]] From e8f984598aa4161319a2056ceb79b1482ba1d673 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 23 Jan 2025 16:12:18 +0000 Subject: [PATCH 2/4] complaining about dead --- ..._clone_easily_dead_when_not_intended_.mdwn | 34 +++++++++++++++++++ 1 file changed, 34 insertions(+) create mode 100644 doc/bugs/dead_clone_easily_dead_when_not_intended_.mdwn diff --git a/doc/bugs/dead_clone_easily_dead_when_not_intended_.mdwn b/doc/bugs/dead_clone_easily_dead_when_not_intended_.mdwn new file mode 100644 index 0000000000..c6b79764cf --- /dev/null +++ b/doc/bugs/dead_clone_easily_dead_when_not_intended_.mdwn @@ -0,0 +1,34 @@ +### Please describe the problem. + +Current syntax of `dead` online at git annex dead [repository ...] [--key somekey ...] says + +`git annex dead [repository ...] [--key somekey ...]` + +which is also incorrect rendering I think since it is + +``` +[d31548v@ndoli tmp]$ git annex dead --help +git-annex dead - hide a lost repository or key + +Usage: git-annex dead [[REPOSITORY ...] | [--key KEY]] + +``` + +so it is EITHER to announce REPOSITORY or a KEY. + +Naive/new/quick users, since many annex commands take file paths as arguments could provide `dead` with both - repository and local paths, e.g. `git annex dead here */*.nii.gz` or alike. But then annex proceeds with marking `here` dead while then erroring out on paths: + +```shell +(datalad-dev) [d78092t@ndoli 1080_wasabi]$ git-annex dead here sub-SID000743/ses-01/func/*.nii +dead here (recording state in git...) +ok +git-annex: there is no available git remote named "sub-SID000743/ses-01/func/sub-SID000743_ses-01_task-hyperalignment_acq-mb8_run-04_bold.nii" +``` + +which is correct/expected behavior given the fact that if RTFM then those are to be taken as repositories. + +But I wondered if may be `git annex` could/should become more "protective" and fail early if any of provided repositories is "not available"? + + +[[!meta author=yoh]] +[[!tag projects/openneuro]] From 103ec0123fb3a74cbea47e832b36388a111b4130 Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 23 Jan 2025 21:33:26 +0000 Subject: [PATCH 3/4] Added a comment --- .../comment_2_4da905b6b8c0c0ba31f4379bf6d940e0._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/git-annex-dead/comment_2_4da905b6b8c0c0ba31f4379bf6d940e0._comment diff --git a/doc/git-annex-dead/comment_2_4da905b6b8c0c0ba31f4379bf6d940e0._comment b/doc/git-annex-dead/comment_2_4da905b6b8c0c0ba31f4379bf6d940e0._comment new file mode 100644 index 0000000000..9e736aefaf --- /dev/null +++ b/doc/git-annex-dead/comment_2_4da905b6b8c0c0ba31f4379bf6d940e0._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 2" + date="2025-01-23T21:33:25Z" + content=""" +d'oh -- it is `git annex semitrust here` to return the \"trust\" into a dead beast ;) +"""]] From f1b64f0415da605ebaf12a1b6586c864b9d63f8d Mon Sep 17 00:00:00 2001 From: "beryllium@5bc3c32eb8156390f96e363e4ba38976567425ec" Date: Fri, 24 Jan 2025 08:04:27 +0000 Subject: [PATCH 4/4] Added a comment --- ...t_4_2270f72a453d8a75a2e050c82561e4ae._comment | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment diff --git a/doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment b/doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment new file mode 100644 index 0000000000..a469b42363 --- /dev/null +++ b/doc/git-annex-whereused/comment_4_2270f72a453d8a75a2e050c82561e4ae._comment @@ -0,0 +1,16 @@ +[[!comment format=mdwn + username="beryllium@5bc3c32eb8156390f96e363e4ba38976567425ec" + nickname="beryllium" + avatar="http://cdn.libravatar.org/avatar/62b67d68e918b381e7e9dd6a96c16137" + subject="comment 4" + date="2025-01-24T08:04:27Z" + content=""" +I don't know if this is expected behaviour, but for some files I imported from an importtree, when I use git-annex whereused --key with the correct key, nothing is shown unless I also add --historical + +And then I am shown the importtree branch information. It doesn't seem to make sense to me. The file is definitely present, and git-annex whereis confirms this, as does git-annex lock/unlock + +Willing to add more context if this is a little too vague + +Shaddy Baddah (beryllium at shaddybaddah dot name) + +"""]]