Closed jsheunis closed 1 year ago
Seems like the issue was introduced with datalad 0.17.0. Relevant issue here: https://github.com/datalad/datalad/issues/7000. Interim solution: downgrade datalad version to <0.17 until fix is released for datalad.
setup.cfg
currently states datalad >= 0.16.7
)0.17.7
I think this can be safely closing (although I wonder whether that would justify bumping DataLad requirement - but I think a closed issue still carries the information).
This was the last time it ran successfully: https://github.com/datalad/datalad-neuroimaging/actions/runs/2320161731