From cb952e762d99606ce51b0dd41555ad46874674bd Mon Sep 17 00:00:00 2001 From: yarikoptic Date: Thu, 16 May 2024 22:22:50 +0000 Subject: [PATCH] Added a comment --- ...mment_1_545214ce157660084b1c4880c2cd0775._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_1_545214ce157660084b1c4880c2cd0775._comment diff --git a/doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_1_545214ce157660084b1c4880c2cd0775._comment b/doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_1_545214ce157660084b1c4880c2cd0775._comment new file mode 100644 index 0000000000..7030434047 --- /dev/null +++ b/doc/bugs/multiple_records_in_remote.log_for_the_same_remote/comment_1_545214ce157660084b1c4880c2cd0775._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="yarikoptic" + avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4" + subject="comment 1" + date="2024-05-16T22:22:50Z" + content=""" +dang -- doing that dance of remove and re-enableremote actually addressed it (I did feel that we had similar case before) -- it removed duplicate entries in `remote.log`. + +and looking at https://github.com/OpenNeuroDatasets/ds000001/blob/git-annex/remote.log -- there is no duplicates. + +So it feels like it is just a matter of git-annex to be able to somehow trigger fixup for a user without needing to do the whole investigation and dance of remove/re-enableremote? or at least to warn somehow whenever such a situation detected +"""]]