[Monotone-devel] Re: Broken database?

[graydon hoare]

Peter Simons wrote:
> graydon hoare writes:
>
>  > there's not much I can recommend at the moment, aside
>  > from waiting for the netsync code.
>
> Is there any time frame when the new code should be
> available? Is it worth to fix the database / repo as-it-is
> now, or shall I wait for the new version?

13 days ago I said it'd take around "two weeks". that was a bit 
optimistic; there are still some missing chunks. it will not be ready by 
tomorrow. it hasn't gotten significantly "worse" over those 13 days, I 
just had less time to work on it than I'd hoped. really only three long 
sittings: the 31st, 1st, and yesterday. it'll still be at least a week 
before I'm ready for a release based on this stuff, if not two. this 
weekend, being valentine's day, will probably see not much hacking.

you can monitor my progress -- I'm posting work to my own depot -- but 
so far it only does the first 2/3 of the protocol: authentication and 
merkle-tree refinement. the remaining third (transfering objects and 
deltas once they're decided on) is decoded, dispatched and ignored.

whether it's worth the time to fix your db.. that depends. I still don't 
know exactly why your logs got out of sync, all I know is that it's a 
possible failure mode, and it seems to be a persistent problem. the 
obvious thing to try is just moving your depot database aside and 
re-posting everything from a "working" client db ("monotone queue 
addtree"), but if that fails there's probably a deeper bug hiding. you 
can try picking at it, or ask me to help, or ignore it and wait. that 
decision is up to you.

are you actually depending on monotone for daily work? if so, perhaps 
it's worth your time to fight the log stuff some more. if you're still 
in the "fooling around" stage, personally, I wouldn't bother.

-graydon