# HG changeset patch
# User Siddharth Agarwal <sid0@fb.com>
# Date 1406943018 25200
# Node ID 48e32c2c499b6b06c2e1852f3c8d0a4b43a85265
# Parent  8cab8a5006a5b17727538dd98be8a8704c5fd856
context: call normal on the right object

dirstate.normal is the method that marks files as unchanged/normal.

Rev 20a30cd41d21 started caching dirstate.normal in order to improve
performance. However, there was an error in the patch: taking the wlock, under
some conditions depending on platform, can cause a new dirstate object to be
created. Caching dirstate.normal before calling wlock would then cause the
fixup calls below to be on the old dirstate object, effectively disappearing
into the ether.

On Unix and Unix-like OSes, the condition under which we create a new dirstate
object is 'the dirstate file has been modified since the last time we opened
it'. This happens pretty rarely, so the object is usually the same -- there's
little impact.

On Windows, the condition is 'always'. This means files in the lookup state are
never marked normal, so the bug has a serious performance impact since all the
files in the lookup state are re-read every time hg status is run.

diff -r 8cab8a5006a5 -r 48e32c2c499b mercurial/context.py
--- a/mercurial/context.py	Fri Aug 01 18:23:18 2014 -0500
+++ b/mercurial/context.py	Fri Aug 01 18:30:18 2014 -0700
@@ -1341,8 +1341,10 @@
             try:
                 # updating the dirstate is optional
                 # so we don't wait on the lock
+                # wlock can invalidate the dirstate, so cache normal _after_
+                # taking the lock
+                wlock = self._repo.wlock(False)
                 normal = self._repo.dirstate.normal
-                wlock = self._repo.wlock(False)
                 try:
                     for f in fixup:
                         normal(f)