3 subject="""comment 3"""
4 date="2022-05-31T16:40:25Z"
6 This certianly looks like a file handle leak in git-annex filter-process..
8 A workaround for you would be to run:
10 git config --unset filter.annex.process
12 I have tried to reproduce this. I made a repository with 10000 files,
13 all annexed and unlocked. I upgraded it to repository version 9. I checked
14 out a commit where all the files were not present yet, and then checked out
15 a commit that had all the files present. It did not fail, and also I never
16 saw it having more than a few files open.
18 So there must be something else about your repository that is needed to
21 (Weirdly, signal 15 is SIGTERM, so I don't know what would have caused it to
22 receive that signal unless it was ctrl-c'd.)