On Mon, Feb 27, 2012 at 07:36:39AM -0800, Jason Wong wrote: > This is true. We have seen the bug happen before. The first occurence > of this that we had seen was Dec. 7th, 2011, a few days after we went > from 1.6.16 to 1.7.1. That was the first time we had seen that happen. > At the time, we did not know about the cause and the developer who > had encountered the error didn't report it and was able to work > around it. From the Apache logs we have: > > [Wed Dec 07 15:16:36 2011] [error] [client 10.2.3.1] predecessor > count for the root node-revision is wrong: found 59444, > committing r59478 [409, #160004]
Just to be clear: These errors emitted by the 1.7.1 server prevent the bug from corrupting new revisions. With a 1.6 server the problem would go unnoticed and create bad revision data. When this corruption occurs, the repository still works. But the history links for affected revisions are incorrect.
