Interesting, thanks for the report. Can you give me a way to reproduce?
Ah shit, already deleted it. I was getting “too many files open error” so I started applying a pijul pull
on batches of 5; after applying the second to last batch the error appeared. :/
After that error I deleted the repo and cloned from scratch.
(I should really implement a live reload of comments on this page).
Is this an old repository, or a recently-cloned one? Is this a public repo?
It is this repo, was pulling new pijul changes.
Ok, was it an old-ish instance you had from months ago, in which you pulled new patches?
I agree that the “too many files open” issue is problematic, it even kills the Nest sometimes, and wouldn’t be too hard to fix.
Not really old-ish, about 15 changes behind the repo. (Was still tagged as alpha.49) Maybe a week at most.
Ok, this is a bit scary. I know you don’t have the repository anymore, but do you remember when you first cloned it?
Probably about a month or so ago, some days after the format last changed. It was 15 changes behind nest when I tried to pull by batches of 5.
News about this: your report prompted me to read the source code of Sanakirja once again, and to run a few extra tests to try and increase the coverage. I found one pretty serious bug, which could cause both a leak (i.e. parts of the database file not referenced anywhere, and not listed as free), and a double free.
I just published a new version of Pijul with the fix. Thanks again!