Closed FeHoff closed 4 months ago
I can replicate this. I have determined the behavior to change after the merge of https://github.com/datalad/datalad-next/pull/669
Specifically, c5b36205ca67c785461d6162104ca8dc478b1075 is still working, but 096a567e36202efe1f1afba250b0b1f62f2af7fc is not. The breakage is still present post-1.4.0 in a8123960eb31227def060fc232f0f811731a62e5
It got fixed via 905b99bd6c3e2c436ba87d097838a06d3ae37eeb in https://github.com/datalad/datalad-next/pull/701
Ping @christian-monch
I get the following warning but the dataset is setup with the yoda procedure as expected.