Hi darcs team,

I am getting the above error on darcs commands like add, pull, record, 
...  Repairing does not help.

localhost:Agda2 abel$ darcs repair
The repository is already consistent, no changes made. 

localhost:Agda2 abel$ darcs add test/succeed/Issue366.agda 

darcs: Codec.Compression.Zlib: premature end of compressed stream

I noticed the problem with darcs 2.4.4, then upgraded to 2.5 (release), 
but it had no effect.

The broken repository is here:

   http://www2.tcs.ifi.lmu.de/~abel/Agda2-darcs-broken.tgz

I am using unison between different architectures (Mac / Linux) which 
also synchronizes the darcs patches.  So far I never had a problem with 
this strategy.  Could that have triggered the problem?

Anyway, how to proceed from here?  I have unrecorded changes I'd like to 
save.

Cheers,
Andreas



-- 
Andreas Abel  <><      Du bist der geliebte Mensch.

Theoretical Computer Science, University of Munich
Oettingenstr. 67, D-80538 Munich, GERMANY

andreas.abel@ifi.lmu.de
http://www2.tcs.ifi.lmu.de/~abel/

The pristine tree seems to be corrupt in that a file is missing in 
_darcs/pristine.hashed (strace shows darcs failing to open it).

I don't know why darcs repair doesn't detect this (though one guess just 
occurs to me - it might only compare the hashes of pristine against the 
replayed repo, without checking that pristine is actually ok.) That 
seems like a real bug in darcs.

A simple workaround seems to be to rm -rf _darcs/pristine.hashed first, 
then rerun darcs repair.

It's not obvious how unison might have triggered the problem, but I 
guess if it got confused about a new or deleted file it may have got 
things wrong.

Thanks for the quick answer!

On 11/22/10 1:15 AM, Ganesh Sittampalam wrote:
>
> Ganesh Sittampalam<ganesh@earth.li>  added the comment:
>
> The pristine tree seems to be corrupt in that a file is missing in
> _darcs/pristine.hashed (strace shows darcs failing to open it).
>
> I don't know why darcs repair doesn't detect this (though one guess just
> occurs to me - it might only compare the hashes of pristine against the
> replayed repo, without checking that pristine is actually ok.) That
> seems like a real bug in darcs.
>
> A simple workaround seems to be to rm -rf _darcs/pristine.hashed first,
> then rerun darcs repair.

Darcs does not seem to like this:

localhost:Agda2 abel$ darcs check

darcs failed:  Pristine tree doesn't exist.

>
> It's not obvious how unison might have triggered the problem, but I
> guess if it got confused about a new or deleted file it may have got
> things wrong.
>
> ----------
> status: unknown ->  need-action
>
> __________________________________
> Darcs bug tracker<bugs@darcs.net>
> <http://bugs.darcs.net/issue2001>
> __________________________________
>

-- 
Andreas Abel  <><      Du bist der geliebte Mensch.

Theoretical Computer Science, University of Munich
Oettingenstr. 67, D-80538 Munich, GERMANY

andreas.abel@ifi.lmu.de
http://www2.tcs.ifi.lmu.de/~abel/

Ah ok, creating an empty _darcs/pristine.hashed directory and then darcs 
repair restores it.

Thanks, it seems to work again now!

Cheers,
Andreas

On 11/22/10 1:22 AM, Andreas Abel wrote:
> Thanks for the quick answer!
>
> On 11/22/10 1:15 AM, Ganesh Sittampalam wrote:
>>
>> Ganesh Sittampalam<ganesh@earth.li> added the comment:
>>
>> The pristine tree seems to be corrupt in that a file is missing in
>> _darcs/pristine.hashed (strace shows darcs failing to open it).
>>
>> I don't know why darcs repair doesn't detect this (though one guess just
>> occurs to me - it might only compare the hashes of pristine against the
>> replayed repo, without checking that pristine is actually ok.) That
>> seems like a real bug in darcs.
>>
>> A simple workaround seems to be to rm -rf _darcs/pristine.hashed first,
>> then rerun darcs repair.
>
> Darcs does not seem to like this:
>
> localhost:Agda2 abel$ darcs check
>
> darcs failed: Pristine tree doesn't exist.
>
>>
>> It's not obvious how unison might have triggered the problem, but I
>> guess if it got confused about a new or deleted file it may have got
>> things wrong.
>>
>> ----------
>> status: unknown -> need-action
>>
>> __________________________________
>> Darcs bug tracker<bugs@darcs.net>
>> <http://bugs.darcs.net/issue2001>
>> __________________________________
>>
>

-- 
Andreas Abel  <><      Du bist der geliebte Mensch.

Theoretical Computer Science, University of Munich
Oettingenstr. 67, D-80538 Munich, GERMANY

andreas.abel@ifi.lmu.de
http://www2.tcs.ifi.lmu.de/~abel/

I ran into this problem with darcs 2.5, and managed to fix it thanks to 
the instructions in this page. Thanks!

However the error message could be more helpful, and the fact that darcs 
check does not notice the problem looks like a real bug to me.

Pepe, do you have any idea how you got into that situation? Just trying to 
get some sense of how it might happen.

FWIW, we had the same issue in Agda. It seems that problem was too many
files open

  https://github.com/agda/agda/issues/1814

The same issue is also reported in Cabal

  https://github.com/haskell/cabal/issues/2001

(The issue number in Cabal and Darcs are the same, what a coincidence!)

Hi Andrés,

could you describe the situation that leads to this error message, and
confirm that this occurs with the current Darcs version ?

thanks

Guillaume

2016-09-05 21:05 GMT-03:00 Andrés Sicard-Ramírez <bugs@darcs.net>:
>
> Andrés Sicard-Ramírez <asr@eafit.edu.co> added the comment:
>
> FWIW, we had the same issue in Agda. It seems that problem was too many
> files open
>
>   https://github.com/agda/agda/issues/1814
>
> The same issue is also reported in Cabal
>
>   https://github.com/haskell/cabal/issues/2001
>
> (The issue number in Cabal and Darcs are the same, what a coincidence!)
>
> __________________________________
> Darcs bug tracker <bugs@darcs.net>
> <http://bugs.darcs.net/issue2001>
> __________________________________
> _______________________________________________
> darcs-devel mailing list
> darcs-devel@darcs.net
> http://lists.osuosl.org/mailman/listinfo/darcs-devel

I'm not reporting the error in Darcs. I only said we had an issue with
the *same error message* in Agda.

We have no chance to find out how the repo became broken. So I changed 
the title to refer to what we can fix, namely that repair does not detect 
the broken pristine here.

I forgot to mention that a comparison between the old pristine dir 
and the repaired one shows that there are no differences between 
files common to both directories (there are only 6 of them). And 
that an attempt to clone the broken repo with a current darcs 
complains about a missing pristine file (rather than the obscure 
zlib error from the original bug report).

The following patch sent by Ben Franksen <ben.franksen@online.de> updated issue issue2001 with
status=resolved;resolvedin=2.15.0 HEAD

* resolve issue2001: repair fails to detect missing pristine files 
Ignore-this: 316662672f7dea1cb73569db8e3c922e9bb82df45f090cf101a3e1b806acc793a5d96a86c9746e73

The trick is to call darcsUpdateHashes after reading the pristine tree. This
makes it fail when there are missing pristine files.