3 avatar="http://cdn.libravatar.org/avatar/f11e9c84cb18d26a1748c33b48c924b4"
4 subject="mystery resolved"
5 date="2022-07-01T19:19:30Z"
7 Ok, resolved mystery for myself:
9 > So if you were using an url without .git before, it seems like it would have failed to detect a uuid after enabling the special remote.
11 yes -- if `initremote` failed to detect uuid it
13 - didn't exit with non-0 (i.e. initremote call succeeded, our code passed through)
14 - produced a \"funky\" looking remotes.log entry without UUID:
17 (git-annex)lena:~/.tmp/datalad_temp_test_as_common_datasourcek5ozqwqd[dl-test-branch]git-annex
18 $> git show git-annex:remote.log
19 autoenable=true location=http://127.0.0.1:41311/ name=fresh-sr type=git timestamp=1656702874.867345813s
20 0392395d-c1a2-4791-ba6a-e932f1392c34 autoenable=true location=http://127.0.0.1:41311/.git name=mike2 type=git timestamp=165670282
23 and our test was working before because apparently we had that type=git remote already added with the correct (with `.git`) url (as you can see above) so as long as initremote didn't crash, we were \"happy\" ;) a little more info could be found in [our datalad issue](https://github.com/datalad/datalad/issues/6779)