Re: [Monotone-devel] 2 explicit merges which are the same, apart from destination branch => invariant violation

[Nathaniel Smith]

On Tue, Jun 06, 2006 at 08:02:26AM +1000, Daniel Carosone wrote:
> Clearly there is a user interface issue here in the way the error is
> detected and reported which could be more helpful or less panicky, and
> monotone could perhaps be smarter in how it responds to some
> situations.
> 
> I presume this test is a guard against, among other things, the very
> faint possibility of a hash collision creating two revisions with the
> same id but which aren't really identical.  It may also be a guard
> against some other kinds of esoteric bugs in the code, not necessarily
> any specific or anticipated problem. Monotone is full of careful
> checking against internal consistency failures like this.

Well, it's almost certainly just a bug :-).  Sometimes our consistency
checking is a little _too_ zealous.  (Better that than the
alternative, but still a bug.)

-- Nathaniel

-- 
Sentience can be such a burden.