comparison hgext/largefiles/overrides.py @ 48063:e4c79a1a0b67

dirstate: drop some safety assert in largefile

The code involved in `set_possibly_dirty` is now simpler and safe to use even
in the cases that the assert covered. So we can drop this assert.

It was the last user of `merged_removed` and `from_p2_removed`.

Differential Revision: https://phab.mercurial-scm.org/D11511

48062:46d1b75648f4

                continue
            lfutil.updatestandin(repo, lfile, fstandin)
        # mark all clean largefiles as dirty, just in case the update gets
        # interrupted before largefiles and lfdirstate are synchronized
        for lfile in oldclean:
            entry = lfdirstate._map.get(lfile)
            assert not (entry.merged_removed or entry.from_p2_removed)
            lfdirstate.set_possibly_dirty(lfile)
        lfdirstate.write()

        oldstandins = lfutil.getstandinsstate(repo)
        wc = kwargs.get('wc')

48063:e4c79a1a0b67

                continue
            lfutil.updatestandin(repo, lfile, fstandin)
        # mark all clean largefiles as dirty, just in case the update gets
        # interrupted before largefiles and lfdirstate are synchronized
        for lfile in oldclean:
            lfdirstate.set_possibly_dirty(lfile)
        lfdirstate.write()

        oldstandins = lfutil.getstandinsstate(repo)
        wc = kwargs.get('wc')