iter_annexworktree fails on Windows 10 with git-annex
#559
Assignees
Comments
christian-monch
added a commit
to christian-monch/datalad-next
that referenced
this issue
Dec 7, 2023
This commit fixes issue datalad#559. It allows `itemize` to any of multiple line-separators to separate the output of `git annex find`. This takes care of the fact that some git-annex versions will output an unrequested `'\r'` in addition to a requested `'\n'`.
mih
added a commit
that referenced
this issue
Dec 7, 2023
fix issue #559, a Windows line endings-related bug
|
Fix with #560 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
On a Windows installation (Windows 10Pro, 22H2) with git-annex version: 10.20230803-gd467c70ef7, the tests of
iter_annexworktreefail.The reason is that a key in the format
'${key}\r\n'is written out by git-annex find, even though the format'${key}\n'is specified (the output contains an additional'\r').The
itemize-function that parses the output of git-annex find expects a singleb'\n'as key-terminator, and fails therefore to properly yield individual keys.This can be fixed by setting the terminator to
Nonewhich allowsitemizeto use a number of different separators, e.g.b'\r'andb'\r\n'.The text was updated successfully, but these errors were encountered: