mercurial/dirstate.py

50146:8ba5028de859

        """Wrap a status operation

        This context is not mutally exclusive with the `changing_*` context. It
        also do not warrant for the `wlock` to be taken.

        If the wlock is taken, this context will (in the future) behave in a
        simple way, and ensure the data are scheduled for write when leaving
        the top level context.

        If the lock is not taken, it will only warrant that the data are either
        committed (written) and rolled back (invalidated) when exiting the top
        level context. The write/invalidate action must be performed by the
        wrapped code.

        D: try to take the w-lock (this will invalidate the changes if they were raced)
        E0: if dirstate changed on disk → discard change (done by dirstate internal)
        E1: elif lock was acquired → write the changes
        E2: else → discard the changes
        """
        is_changing = self.is_changing_any
        has_tr = repo.currenttransaction is not None
        nested = bool(self._running_status)

        first_and_alone = not (is_changing or has_tr or nested)

        # enforce no change happened outside of a proper context.
        if first_and_alone and self._dirty:
            has_tr = repo.currenttransaction() is not None
            if not has_tr and self._changing_level == 0 and self._dirty:
                msg = "entering a status context, but dirstate is already dirty"
                raise error.ProgrammingError(msg)

        self._running_status += 1
        try:
            yield
        except Exception:
            self.invalidate()
            raise
        finally:
            self._running_status -= 1
            if self._invalidated_context:
                self.invalidate()

    @contextlib.contextmanager
    @check_invalidated
    def _changing(self, repo, change_type):
        if repo.currentwlock() is None:

50147:0be70c7b609c

        """Wrap a status operation

        This context is not mutally exclusive with the `changing_*` context. It
        also do not warrant for the `wlock` to be taken.

        If the wlock is taken, this context will behave in a simple way, and
        ensure the data are scheduled for write when leaving the top level
        context.

        If the lock is not taken, it will only warrant that the data are either
        committed (written) and rolled back (invalidated) when exiting the top
        level context. The write/invalidate action must be performed by the
        wrapped code.

        D: try to take the w-lock (this will invalidate the changes if they were raced)
        E0: if dirstate changed on disk → discard change (done by dirstate internal)
        E1: elif lock was acquired → write the changes
        E2: else → discard the changes
        """
        has_lock = repo.currentwlock() is not None
        is_changing = self.is_changing_any
        tr = repo.currenttransaction()
        has_tr = tr is not None
        nested = bool(self._running_status)

        first_and_alone = not (is_changing or has_tr or nested)

        # enforce no change happened outside of a proper context.
        if first_and_alone and self._dirty:
            has_tr = repo.currenttransaction() is not None
            if not has_tr and self._changing_level == 0 and self._dirty:
                msg = "entering a status context, but dirstate is already dirty"
                raise error.ProgrammingError(msg)

        should_write = has_lock and not (nested or is_changing)

        self._running_status += 1
        try:
            yield
        except Exception:
            self.invalidate()
            raise
        finally:
            self._running_status -= 1
            if self._invalidated_context:
                should_write = False
                self.invalidate()

        if should_write:
            assert repo.currenttransaction() is tr
            self.write(tr)

    @contextlib.contextmanager
    @check_invalidated
    def _changing(self, repo, change_type):
        if repo.currentwlock() is None: