dirstate incorrectly updated, modified files not shown

Tom Karzes tom.karzes at magnumsemi.com
Wed Jan 7 00:26:12 UTC 2009


I finally tracked this down.  It turned out to be a genuine Mercurial bug,
and had nothing to do with the extension we've been using.  I have confirmed
that the bug in releases 1.0.1 through 1.1.2.  Starting with 1.1, the bug
became more difficult to reproduce, but it still exists.  Here's the bug
report that I filed with selenic:

    http://www.selenic.com/mercurial/bts/issue1456

Tom



Tom Karzes wrote:
> 
> We've been seeing a bug in which "hg status", "hg commit", etc. are
> ignoring some locally modified files.  I believe this is due to
> .hg/dirstate having been incorrectly updated to show their new modified
> times, sizes, etc., even though they have been changed since they were
> last updated from the repository.  You can "fix" the problem by touching
> the files that have been changed, which causes Mercurial to actually look
> at their contents to determine if they've been modified, but the problem
> is that you often don't know when you need to do this.
> 
> The only thing out of the ordinary that we've been doing is using an
> extension that operates on multiple repositories at once (not the forest
> extension).  It will sometimes have multiple live repo classes, switching
> between one and another without changing the current working directory. 
> But it does not attempt to do any direct repository manipulation - it goes
> through the normal repo and command interfaces.
> 
> Has anyone else encountered this problem?  It seems to arise quite often
> for us, but it has proven to be difficult to deterministically reproduce.
> 
> 

-- 
View this message in context: http://www.nabble.com/dirstate-incorrectly-updated%2C-modified-files-not-shown-tp21101981p21322553.html
Sent from the Mercurial mailing list archive at Nabble.com.




More information about the Mercurial mailing list