On 11/24/07, Juliusz Chroboczek <[EMAIL PROTECTED]> wrote: > > | darcs: getCurrentDirectory: resource exhausted (Too many open files) > > > This sounds like a Darcs bug, but it's not one I have heard before. > > I've definitely seen this issue, but I don't remember how it ended. > I seem to recall that it's due to Darcs opening a number of immutable > files using unsafePerformIO, and due to lazy evaluation, they don't > get closed until some later time. > > I don't remember what the solution was. In any case, Darcs should > leave your repository in a sane state (but run ``darcs check'' just in > case).
I experienced this problem once -- during a pull, and apparently after Darcs had written out the "the following files had conflicts" bit -- and although it left the *repo* in a sane state, the working directory was all in pieces. This is a general problem with Darcs: the working directory operations are not atomic, so any repo operation that changes the working directory risks applying changes that are subsequently not associated with their patches. Alexander. _______________________________________________ darcs-devel mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-devel
