2022-01-06 01:42:23 +03:00
|
|
|
# Portions Copyright (c) Meta Platforms, Inc. and affiliates.
|
2019-11-01 22:33:28 +03:00
|
|
|
#
|
|
|
|
# This software may be used and distributed according to the terms of the
|
|
|
|
# GNU General Public License version 2.
|
|
|
|
|
2009-04-26 03:13:08 +04:00
|
|
|
# dirstate.py - working directory tracking for mercurial
|
|
|
|
#
|
2022-05-17 04:40:28 +03:00
|
|
|
# Copyright 2005-2007 Olivia Mackall <olivia@selenic.com>
|
2009-04-26 03:13:08 +04:00
|
|
|
#
|
|
|
|
# This software may be used and distributed according to the terms of the
|
2010-01-20 07:20:08 +03:00
|
|
|
# GNU General Public License version 2 or any later version.
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
# pyre-strict
|
|
|
|
|
2015-12-22 08:38:53 +03:00
|
|
|
from __future__ import absolute_import
|
|
|
|
|
2017-05-19 00:10:30 +03:00
|
|
|
import contextlib
|
2015-12-22 08:38:53 +03:00
|
|
|
import errno
|
|
|
|
import os
|
2022-03-24 23:40:54 +03:00
|
|
|
import tempfile
|
2019-10-02 20:56:15 +03:00
|
|
|
import weakref
|
2020-08-12 07:43:21 +03:00
|
|
|
from typing import (
|
|
|
|
BinaryIO,
|
|
|
|
Callable,
|
apply import merging for fbcode (4 of 11)
Summary:
Applies new import merging and sorting from µsort v1.0.
When merging imports, µsort will make a best-effort to move associated
comments to match merged elements, but there are known limitations due to
the diynamic nature of Python and developer tooling. These changes should
not produce any dangerous runtime changes, but may require touch-ups to
satisfy linters and other tooling.
Note that µsort uses case-insensitive, lexicographical sorting, which
results in a different ordering compared to isort. This provides a more
consistent sorting order, matching the case-insensitive order used when
sorting import statements by module name, and ensures that "frog", "FROG",
and "Frog" always sort next to each other.
For details on µsort's sorting and merging semantics, see the user guide:
https://usort.readthedocs.io/en/stable/guide.html#sorting
Reviewed By: lisroach
Differential Revision: D36402162
fbshipit-source-id: 6d180e9003d466c4f866fc9d454c6531766ca1dd
2022-05-15 22:53:03 +03:00
|
|
|
cast,
|
2020-08-12 07:43:21 +03:00
|
|
|
Dict,
|
|
|
|
Generator,
|
|
|
|
Iterable,
|
|
|
|
List,
|
|
|
|
Optional,
|
|
|
|
Sequence,
|
|
|
|
Set,
|
|
|
|
Tuple,
|
|
|
|
Type,
|
|
|
|
Union,
|
|
|
|
)
|
|
|
|
|
|
|
|
import bindings
|
2020-02-18 22:37:39 +03:00
|
|
|
|
|
|
|
# Using an absolute import here allows us to import localrepo even though it
|
|
|
|
# circularly imports us.
|
|
|
|
import edenscm.mercurial.localrepo
|
2020-02-22 00:48:20 +03:00
|
|
|
from edenscmnative import parsers
|
2015-12-22 08:38:53 +03:00
|
|
|
|
|
|
|
from . import (
|
2020-08-12 07:43:21 +03:00
|
|
|
context,
|
2015-12-22 08:38:53 +03:00
|
|
|
encoding,
|
|
|
|
error,
|
2019-10-09 02:43:10 +03:00
|
|
|
filesystem,
|
2015-12-22 08:38:53 +03:00
|
|
|
match as matchmod,
|
|
|
|
pathutil,
|
2019-03-26 05:22:16 +03:00
|
|
|
perftrace,
|
2016-11-06 01:40:33 +03:00
|
|
|
pycompat,
|
2015-12-22 08:38:53 +03:00
|
|
|
scmutil,
|
2020-08-12 07:43:21 +03:00
|
|
|
transaction,
|
2018-10-10 13:49:30 +03:00
|
|
|
treedirstate,
|
2018-06-11 23:49:45 +03:00
|
|
|
treestate,
|
2017-02-20 19:20:59 +03:00
|
|
|
txnutil,
|
2020-02-18 22:37:39 +03:00
|
|
|
ui as ui_mod,
|
2015-12-22 08:38:53 +03:00
|
|
|
util,
|
2020-02-18 22:37:39 +03:00
|
|
|
vfs,
|
2015-12-22 08:38:53 +03:00
|
|
|
)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
from .i18n import _
|
2019-04-04 21:23:55 +03:00
|
|
|
from .node import hex, nullid
|
2020-01-29 18:38:41 +03:00
|
|
|
from .pycompat import encodeutf8
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2018-10-01 17:15:19 +03:00
|
|
|
_rangemask = 0x7FFFFFFF
|
2012-03-01 19:42:49 +04:00
|
|
|
|
parsers: inline fields of dirstate values in C version
Previously, while unpacking the dirstate we'd create 3-4 new CPython objects
for most dirstate values:
- the state is a single character string, which is pooled by CPython
- the mode is a new object if it isn't 0 due to being in the lookup set
- the size is a new object if it is greater than 255
- the mtime is a new object if it isn't -1 due to being in the lookup set
- the tuple to contain them all
In some cases such as regular hg status, we actually look at all the objects.
In other cases like hg add, hg status for a subdirectory, or hg status with the
third-party hgwatchman enabled, we look at almost none of the objects.
This patch eliminates most object creation in these cases by defining a custom
C struct that is exposed to Python with an interface similar to a tuple. Only
when tuple elements are actually requested are the respective objects created.
The gains, where they're expected, are significant. The following tests are run
against a working copy with over 270,000 files.
parse_dirstate becomes significantly faster:
$ hg perfdirstate
before: wall 0.186437 comb 0.180000 user 0.160000 sys 0.020000 (best of 35)
after: wall 0.093158 comb 0.100000 user 0.090000 sys 0.010000 (best of 95)
and as a result, several commands benefit:
$ time hg status # with hgwatchman enabled
before: 0.42s user 0.14s system 99% cpu 0.563 total
after: 0.34s user 0.12s system 99% cpu 0.471 total
$ time hg add new-file
before: 0.85s user 0.18s system 99% cpu 1.033 total
after: 0.76s user 0.17s system 99% cpu 0.931 total
There is a slight regression in regular status performance, but this is fixed
in an upcoming patch.
2014-05-28 01:27:41 +04:00
|
|
|
dirstatetuple = parsers.dirstatetuple
|
2014-05-28 04:10:28 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
slowstatuswarning: str = _(
|
2019-10-02 20:56:15 +03:00
|
|
|
"(status will still be slow next time; try to complete or abort "
|
|
|
|
"other source control operations and then run 'hg status' again)\n"
|
2022-02-10 01:26:09 +03:00
|
|
|
)
|
2019-10-02 20:56:15 +03:00
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
class repocache(scmutil.filecache):
|
2012-03-01 19:42:49 +04:00
|
|
|
"""filecache for files in .hg/"""
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def join(self, obj: "dirstate", fname: str) -> str:
|
2012-03-01 19:42:49 +04:00
|
|
|
return obj._opener.join(fname)
|
2007-06-18 22:24:34 +04:00
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
class rootcache(scmutil.filecache):
|
2012-03-01 19:49:59 +04:00
|
|
|
"""filecache for files in the repository root"""
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def join(self, obj: "dirstate", fname: str) -> str:
|
2012-03-01 19:49:59 +04:00
|
|
|
return obj._join(fname)
|
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _getfsnow(vfs: "vfs.abstractvfs") -> int:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Get "now" timestamp on filesystem"""
|
2015-10-13 20:49:17 +03:00
|
|
|
tmpfd, tmpname = vfs.mkstemp()
|
|
|
|
try:
|
2019-12-10 00:09:25 +03:00
|
|
|
return util.fstat(tmpfd).st_mtime
|
2015-10-13 20:49:17 +03:00
|
|
|
finally:
|
|
|
|
os.close(tmpfd)
|
|
|
|
vfs.unlink(tmpname)
|
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
DirstateMapClassType = Union[
|
|
|
|
Type["dirstatemap"],
|
|
|
|
Type[treestate.treestatemap],
|
|
|
|
Type[treedirstate.treedirstatemap],
|
|
|
|
]
|
|
|
|
DirstateMapType = Union[
|
|
|
|
"dirstatemap", treestate.treestatemap, treedirstate.treedirstatemap
|
|
|
|
]
|
|
|
|
ParentChangeCallback = Callable[
|
|
|
|
["dirstate", Tuple[bytes, bytes], Tuple[bytes, bytes]], None
|
|
|
|
]
|
|
|
|
|
|
|
|
|
2022-05-05 05:32:11 +03:00
|
|
|
# pyre-fixme[3]: Return type must be annotated.
|
|
|
|
# pyre-fixme[2]: Parameter must be annotated.
|
2022-01-20 21:19:33 +03:00
|
|
|
def fastreadp1(repopath):
|
|
|
|
"""Read dirstate p1 node without constructing repo or dirstate objects
|
|
|
|
|
|
|
|
This is the first 20-bytes of the dirstate file. All known dirstate
|
|
|
|
implementations (edenfs, treestate, etc.) respect this format.
|
|
|
|
|
|
|
|
Return None if p1 cannot be read.
|
|
|
|
"""
|
|
|
|
try:
|
|
|
|
with open(os.path.join(repopath, ".hg", "dirstate"), "rb") as f:
|
|
|
|
node = f.read(len(nullid))
|
|
|
|
return node
|
|
|
|
except IOError:
|
|
|
|
return None
|
|
|
|
|
|
|
|
|
2005-11-19 09:48:47 +03:00
|
|
|
class dirstate(object):
|
2018-10-10 13:49:30 +03:00
|
|
|
def __init__(
|
2018-10-31 12:48:07 +03:00
|
|
|
self,
|
2022-02-10 01:26:09 +03:00
|
|
|
opener: "vfs.abstractvfs",
|
|
|
|
ui: "ui_mod.ui",
|
|
|
|
root: str,
|
|
|
|
validate: "Callable[[bytes], bytes]",
|
|
|
|
repo: "edenscm.mercurial.localrepo.localrepository",
|
|
|
|
istreestate: bool = False,
|
|
|
|
istreedirstate: bool = False,
|
|
|
|
) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Create a new dirstate object.
|
2009-12-28 01:24:05 +03:00
|
|
|
|
|
|
|
opener is an open()-like callable that can be used to open the
|
|
|
|
dirstate file; root is the root of the directory tracked by
|
|
|
|
the dirstate.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2007-06-18 22:24:34 +04:00
|
|
|
self._opener = opener
|
2010-11-22 21:43:31 +03:00
|
|
|
self._validate = validate
|
2007-06-18 22:24:34 +04:00
|
|
|
self._root = root
|
2022-02-10 01:26:09 +03:00
|
|
|
self._repo: "edenscm.mercurial.localrepo.localrepository" = weakref.proxy(repo)
|
2015-03-05 18:14:22 +03:00
|
|
|
# ntpath.join(root, '') of Python 2.7.9 does not add sep if root is
|
|
|
|
# UNC path pointing to root share (issue4557)
|
2022-02-10 01:26:09 +03:00
|
|
|
self._rootdir: str = pathutil.normasprefix(root)
|
2007-07-22 01:02:09 +04:00
|
|
|
self._dirty = False
|
2012-01-08 21:15:54 +04:00
|
|
|
self._lastnormaltime = 0
|
2007-06-18 22:24:34 +04:00
|
|
|
self._ui = ui
|
2022-02-10 01:26:09 +03:00
|
|
|
self._filecache: "Dict[str, Optional[scmutil.filecacheentry]]" = {}
|
2014-09-05 22:34:29 +04:00
|
|
|
self._parentwriters = 0
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._filename = "dirstate"
|
2022-02-10 01:26:09 +03:00
|
|
|
self._pendingfilename: str = "%s.pending" % self._filename
|
|
|
|
self._plchangecallbacks: "Dict[str, ParentChangeCallback]" = {}
|
|
|
|
self._origpl: "Optional[Tuple[bytes, bytes]]" = None
|
|
|
|
self._updatedfiles: "Set[str]" = set()
|
2018-06-11 23:49:45 +03:00
|
|
|
# TODO(quark): after migrating to treestate, remove legacy code.
|
|
|
|
self._istreestate = istreestate
|
2018-10-10 13:49:30 +03:00
|
|
|
self._istreedirstate = istreedirstate
|
2018-06-11 23:49:45 +03:00
|
|
|
if istreestate:
|
|
|
|
opener.makedirs("treestate")
|
2022-02-10 01:26:09 +03:00
|
|
|
self._mapcls: "DirstateMapClassType" = treestate.treestatemap
|
2018-10-10 13:49:30 +03:00
|
|
|
elif istreedirstate:
|
2020-06-09 02:18:49 +03:00
|
|
|
ui.deprecate("treedirstate", "treedirstate is replaced by treestate")
|
2022-02-10 01:26:09 +03:00
|
|
|
self._mapcls: "DirstateMapClassType" = treedirstate.treedirstatemap
|
2018-06-11 23:49:45 +03:00
|
|
|
else:
|
2020-06-09 02:18:49 +03:00
|
|
|
if "eden" not in repo.requirements:
|
|
|
|
ui.deprecate("dirstatemap", "dirstatemap is replaced by treestate")
|
2022-02-10 01:26:09 +03:00
|
|
|
self._mapcls: "DirstateMapClassType" = dirstatemap
|
2019-10-09 02:43:10 +03:00
|
|
|
self._fs = filesystem.physicalfilesystem(root, self)
|
2014-09-05 22:34:29 +04:00
|
|
|
|
2017-05-19 00:10:30 +03:00
|
|
|
@contextlib.contextmanager
|
2022-02-10 01:26:09 +03:00
|
|
|
def parentchange(self) -> "Generator[None, None, None]":
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Context manager for handling dirstate parents.
|
2017-05-19 00:10:30 +03:00
|
|
|
|
|
|
|
If an exception occurs in the scope of the context manager,
|
|
|
|
the incoherent dirstate won't be written when wlock is
|
|
|
|
released.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2017-05-19 00:10:30 +03:00
|
|
|
self._parentwriters += 1
|
|
|
|
yield
|
|
|
|
# Typically we want the "undo" step of a context manager in a
|
|
|
|
# finally block so it happens even when an exception
|
|
|
|
# occurs. In this case, however, we only want to decrement
|
|
|
|
# parentwriters if the code in the with statement exits
|
|
|
|
# normally, so we don't have a try/finally here on purpose.
|
|
|
|
self._parentwriters -= 1
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def beginparentchange(self) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Marks the beginning of a set of changes that involve changing
|
2014-09-05 22:34:29 +04:00
|
|
|
the dirstate parents. If there is an exception during this time,
|
|
|
|
the dirstate will not be written when the wlock is released. This
|
|
|
|
prevents writing an incoherent dirstate where the parent doesn't
|
|
|
|
match the contents.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
|
|
|
self._ui.deprecwarn(
|
|
|
|
"beginparentchange is obsoleted by the " "parentchange context manager.",
|
|
|
|
"4.3",
|
|
|
|
)
|
2014-09-05 22:34:29 +04:00
|
|
|
self._parentwriters += 1
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def endparentchange(self) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Marks the end of a set of changes that involve changing the
|
2014-09-05 22:34:29 +04:00
|
|
|
dirstate parents. Once all parent changes have been marked done,
|
|
|
|
the wlock will be free to write the dirstate on release.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
|
|
|
self._ui.deprecwarn(
|
|
|
|
"endparentchange is obsoleted by the " "parentchange context manager.",
|
|
|
|
"4.3",
|
|
|
|
)
|
2014-09-05 22:34:29 +04:00
|
|
|
if self._parentwriters > 0:
|
|
|
|
self._parentwriters -= 1
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def pendingparentchange(self) -> bool:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Returns true if the dirstate is in the middle of a set of changes
|
2014-09-05 22:34:29 +04:00
|
|
|
that modify the dirstate parent.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2014-09-05 22:34:29 +04:00
|
|
|
return self._parentwriters > 0
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _map(self) -> "DirstateMapType":
|
2017-11-15 12:07:42 +03:00
|
|
|
"""Return the dirstate contents (see documentation for dirstatemap)."""
|
2017-11-15 12:07:42 +03:00
|
|
|
self._map = self._mapcls(self._ui, self._opener, self._root)
|
2009-04-30 05:47:18 +04:00
|
|
|
return self._map
|
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
@repocache("branch")
|
2022-02-10 01:26:09 +03:00
|
|
|
def _branch(self) -> str:
|
2020-01-29 18:38:41 +03:00
|
|
|
return self._opener.tryreadutf8("branch").strip() or "default"
|
2009-04-30 05:47:18 +04:00
|
|
|
|
2017-09-26 13:56:20 +03:00
|
|
|
@property
|
2022-02-10 01:26:09 +03:00
|
|
|
def _pl(self) -> "Tuple[bytes, bytes]":
|
2017-09-26 13:56:20 +03:00
|
|
|
return self._map.parents()
|
2009-04-30 05:47:18 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def hasdir(self, d: str) -> bool:
|
2017-11-15 12:07:42 +03:00
|
|
|
return self._map.hastrackeddir(d)
|
2012-02-22 19:07:54 +04:00
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
@rootcache(".hgignore")
|
2022-02-10 01:26:09 +03:00
|
|
|
def _ignore(self) -> "matchmod.gitignorematcher":
|
2018-04-10 03:51:24 +03:00
|
|
|
# gitignore
|
2019-04-30 04:19:49 +03:00
|
|
|
globalignores = self._globalignorefiles()
|
|
|
|
return matchmod.gitignorematcher(self._root, "", gitignorepaths=globalignores)
|
2009-04-30 05:47:18 +04:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _slash(self) -> bool:
|
2019-02-07 15:21:59 +03:00
|
|
|
return (
|
|
|
|
self._ui.plain() or self._ui.configbool("ui", "slash")
|
|
|
|
) and pycompat.ossep != "/"
|
2009-04-30 05:47:18 +04:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _checklink(self) -> bool:
|
2009-04-30 05:47:18 +04:00
|
|
|
return util.checklink(self._root)
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _checkexec(self) -> bool:
|
2009-04-30 05:47:18 +04:00
|
|
|
return util.checkexec(self._root)
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _checkcase(self) -> bool:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return not util.fscasesensitive(self._join(".hg"))
|
2009-04-30 05:47:18 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _join(self, f: str) -> str:
|
2008-09-02 17:12:50 +04:00
|
|
|
# much faster than os.path.join()
|
2008-09-02 19:32:07 +04:00
|
|
|
# it's safe because f is always a relative path
|
2008-09-02 17:12:50 +04:00
|
|
|
return self._rootdir + f
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def flagfunc(
|
|
|
|
self, buildfallback: "Callable[[], Callable[[str], str]]"
|
|
|
|
) -> "Callable[[str], str]":
|
2011-10-23 01:12:33 +04:00
|
|
|
if self._checklink and self._checkexec:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2011-10-23 01:12:33 +04:00
|
|
|
def f(x):
|
2013-04-03 22:35:27 +04:00
|
|
|
try:
|
|
|
|
st = os.lstat(self._join(x))
|
|
|
|
if util.statislink(st):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return "l"
|
2013-04-03 22:35:27 +04:00
|
|
|
if util.statisexec(st):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return "x"
|
2013-04-03 22:35:27 +04:00
|
|
|
except OSError:
|
|
|
|
pass
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return ""
|
|
|
|
|
2011-10-23 01:12:33 +04:00
|
|
|
return f
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
fallback: "Callable[[str], str]" = buildfallback()
|
2008-06-26 22:46:34 +04:00
|
|
|
if self._checklink:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2008-06-26 22:46:34 +04:00
|
|
|
def f(x):
|
2008-09-02 17:12:50 +04:00
|
|
|
if os.path.islink(self._join(x)):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return "l"
|
|
|
|
if "x" in fallback(x):
|
|
|
|
return "x"
|
|
|
|
return ""
|
|
|
|
|
2008-06-26 22:46:34 +04:00
|
|
|
return f
|
|
|
|
if self._checkexec:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def f(x: str) -> str:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if "l" in fallback(x):
|
|
|
|
return "l"
|
2011-05-08 22:45:47 +04:00
|
|
|
if util.isexec(self._join(x)):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return "x"
|
|
|
|
return ""
|
|
|
|
|
2008-06-26 22:46:34 +04:00
|
|
|
return f
|
2011-10-23 01:12:33 +04:00
|
|
|
else:
|
|
|
|
return fallback
|
2008-06-26 22:46:34 +04:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _cwd(self) -> str:
|
dirstate: centralize _cwd handling into _cwd method
Before this patch, immediate value is assigned to dirstate._cwd, if
ui.forcecwd is specified at instantiation of dirstate.
But this doesn't work as expected in some cases.
For example, hgweb set ui.forcecwd after instantiation of repo object.
If an extension touches repo.dirstate in its reposetup(), dirstate is
instantiated without setting ui.forcecwd, and dirstate.getcwd()
returns incorrect result.
In addition to it, hgweb.__init__() can take already instantiated repo
object, too. In this case, repo.dirstate might be already
instantiated, even if all enabled extensions don't so in their own
reposetup().
To avoid such issue, this patch centralizes _cwd handling into _cwd
method.
This issue can be reproduced by running test-hgweb-commands.t with
fsmonitor-run-tests.py.
2017-07-02 20:52:40 +03:00
|
|
|
# internal config: ui.forcecwd
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
forcecwd = self._ui.config("ui", "forcecwd")
|
dirstate: centralize _cwd handling into _cwd method
Before this patch, immediate value is assigned to dirstate._cwd, if
ui.forcecwd is specified at instantiation of dirstate.
But this doesn't work as expected in some cases.
For example, hgweb set ui.forcecwd after instantiation of repo object.
If an extension touches repo.dirstate in its reposetup(), dirstate is
instantiated without setting ui.forcecwd, and dirstate.getcwd()
returns incorrect result.
In addition to it, hgweb.__init__() can take already instantiated repo
object, too. In this case, repo.dirstate might be already
instantiated, even if all enabled extensions don't so in their own
reposetup().
To avoid such issue, this patch centralizes _cwd handling into _cwd
method.
This issue can be reproduced by running test-hgweb-commands.t with
fsmonitor-run-tests.py.
2017-07-02 20:52:40 +03:00
|
|
|
if forcecwd:
|
|
|
|
return forcecwd
|
2016-11-22 21:33:11 +03:00
|
|
|
return pycompat.getcwd()
|
2014-02-01 03:13:15 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def getcwd(self) -> str:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Return the path from which a canonical path is calculated.
|
2015-09-20 14:08:22 +03:00
|
|
|
|
|
|
|
This path should be used to resolve file patterns or to convert
|
|
|
|
canonical paths back to file paths for display. It shouldn't be
|
|
|
|
used to get real file paths. Use vfs functions instead.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2014-02-01 03:13:15 +04:00
|
|
|
cwd = self._cwd
|
2010-01-25 09:05:27 +03:00
|
|
|
if cwd == self._root:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return ""
|
2007-06-18 22:24:34 +04:00
|
|
|
# self._root ends with a path separator if self._root is '/' or 'C:\'
|
|
|
|
rootsep = self._root
|
2008-01-09 15:30:35 +03:00
|
|
|
if not util.endswithsep(rootsep):
|
2016-12-17 17:32:50 +03:00
|
|
|
rootsep += pycompat.ossep
|
2007-03-16 06:22:58 +03:00
|
|
|
if cwd.startswith(rootsep):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return cwd[len(rootsep) :]
|
2007-03-16 06:22:58 +03:00
|
|
|
else:
|
|
|
|
# we're outside the repo. return an absolute path.
|
|
|
|
return cwd
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def pathto(self, f: str, cwd: "Optional[str]" = None) -> str:
|
2007-06-09 06:49:12 +04:00
|
|
|
if cwd is None:
|
|
|
|
cwd = self.getcwd()
|
2007-06-18 22:24:34 +04:00
|
|
|
path = util.pathto(self._root, cwd, f)
|
2007-06-09 06:49:12 +04:00
|
|
|
if self._slash:
|
2013-05-17 23:31:06 +04:00
|
|
|
return util.pconvert(path)
|
2007-06-09 06:49:12 +04:00
|
|
|
return path
|
2007-06-09 06:49:12 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __getitem__(self, key: str) -> str:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Return the current state of key (a filename) in the dirstate.
|
2009-12-28 01:24:05 +03:00
|
|
|
|
2009-10-01 23:36:45 +04:00
|
|
|
States are:
|
|
|
|
n normal
|
|
|
|
m needs merging
|
|
|
|
r marked for removal
|
|
|
|
a marked for addition
|
|
|
|
? not tracked
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2020-01-31 01:53:42 +03:00
|
|
|
return self._map.get(key, ("?", 0, 0, 0))[0]
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __contains__(self, key: str) -> bool:
|
2007-06-18 22:24:34 +04:00
|
|
|
return key in self._map
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __iter__(self) -> "Iterable[str]":
|
2020-08-12 07:43:21 +03:00
|
|
|
# pyre-fixme[6]: expected Iterable (maybe PEP 544 will fix this?)
|
2017-08-08 21:53:13 +03:00
|
|
|
return iter(sorted(self._map))
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def items(self) -> "Iterable[Tuple[str, dirstatetuple]]":
|
2020-01-29 03:25:29 +03:00
|
|
|
return pycompat.iteritems(self._map)
|
completion: add a debugpathcomplete command
The bash_completion code uses "hg status" to generate a list of
possible completions for commands that operate on files in the
working directory. In a large working directory, this can result
in a single tab-completion being very slow (several seconds) as a
result of checking the status of every file, even when there is no
need to check status or no possible matches.
The new debugpathcomplete command gains performance in a few simple
ways:
* Allow completion to operate on just a single directory. When used
to complete the right commands, this considerably reduces the
number of completions returned, at no loss in functionality.
* Never check the status of files. For completions that really must
know if a file is modified, it is faster to use status:
hg status -nm 'glob:myprefix**'
Performance:
Here are the commands used by bash_completion to complete, run in
the root of the mozilla-central working dir (~77,000 files) and
another repo (~165,000 files):
All "normal state" files (used by e.g. remove, revert):
mozilla other
status -nmcd 'glob:**' 1.77 4.10 sec
debugpathcomplete -f -n 0.53 1.26
debugpathcomplete -n 0.17 0.41
("-f" means "complete full paths", rather than the current directory)
Tracked files matching "a":
mozilla other
status -nmcd 'glob:a**' 0.26 0.47
debugpathcomplete -f -n a 0.10 0.24
debugpathcomplete -n a 0.10 0.22
We should be able to further improve completion performance once
the critbit work lands. Right now, our performance is limited by
the need to iterate over all keys in the dirstate.
2013-03-22 03:31:28 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
iteritems: "Callable[[dirstate], Iterable[Tuple[str, dirstatetuple]]]" = items
|
2017-05-29 07:00:02 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def parents(self) -> "List[bytes]":
|
2020-08-12 07:43:21 +03:00
|
|
|
# (This always returns a list of length 2. Perhaps we should change it to
|
|
|
|
# return a tuple instead.)
|
2010-11-22 21:43:31 +03:00
|
|
|
return [self._validate(p) for p in self._pl]
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def p1(self) -> bytes:
|
2011-04-05 00:52:55 +04:00
|
|
|
return self._validate(self._pl[0])
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def p2(self) -> bytes:
|
2011-04-05 00:52:55 +04:00
|
|
|
return self._validate(self._pl[1])
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def branch(self) -> str:
|
2010-11-25 00:56:32 +03:00
|
|
|
return encoding.tolocal(self._branch)
|
2007-03-14 02:50:02 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def setparents(self, p1: bytes, p2: bytes = nullid) -> "Dict[str, str]":
|
2012-04-30 00:25:55 +04:00
|
|
|
"""Set dirstate parents to p1 and p2.
|
|
|
|
|
|
|
|
When moving from two parents to one, 'm' merged entries a
|
|
|
|
adjusted to normal and previous copy records discarded and
|
|
|
|
returned by the call.
|
|
|
|
|
|
|
|
See localrepo.setparents()
|
|
|
|
"""
|
2014-09-05 22:37:44 +04:00
|
|
|
if self._parentwriters == 0:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
raise ValueError(
|
|
|
|
"cannot set dirstate parent without "
|
|
|
|
"calling dirstate.beginparentchange"
|
|
|
|
)
|
2014-09-05 22:37:44 +04:00
|
|
|
|
2017-09-26 13:56:20 +03:00
|
|
|
self._dirty = True
|
rebase: skip resolved but emptied revisions
When rebasing, if a conflict occurs and is resolved in a way the rebased
revision becomes empty, it is not skipped, unlike revisions being emptied
without conflicts.
The reason is:
- File 'x' is merged and resolved, merge.update() marks it as 'm' in the
dirstate.
- rebase.concludenode() calls localrepo.commit(), which calls
localrepo.status() which calls dirstate.status(). 'x' shows up as 'm' and is
unconditionnally added to the modified files list, instead of being checked
again.
- localrepo.commit() detects 'x' as changed an create a new revision where only
the manifest parents and linkrev differ.
Marking 'x' as modified without checking it makes sense for regular merges. But
in rebase case, the merge looks normal but the second parent is usually
discarded. When this happens, 'm' files in dirstate are a bit irrelevant and
should be considered 'n' possibly dirty instead. That is what the current patch
does.
Another approach, maybe more efficient, would be to pass another flag to
merge.update() saying the 'branchmerge' is a bit of a lie and recordupdate()
should call dirstate.normallookup() instead of merge().
It is also tempting to add this logic to dirstate.setparents(), moving from two
to one parent is what invalidates the 'm' markers. But this is a far bigger
change to make.
v2: succumb to the temptation and move the logic in dirstate.setparents(). mpm
suggested trying _filecommit() first but it is called by commitctx() which
knows nothing about the dirstate and comes too late into the game. A second
approach was to rewrite the 'm' state into 'n' on the fly in dirstate.status()
which failed for graft in the following case:
$ hg init repo
$ cd repo
$ echo a > a
$ hg ci -qAm0
$ echo a >> a
$ hg ci -m1
$ hg up 0
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg mv a b
$ echo c > b
$ hg ci -m2
created new head
$ hg graft 1 --tool internal:local
grafting revision 1
$ hg --config extensions.graphlog= glog --template '{rev} {desc|firstline}\n'
@ 3 1
|
o 2 2
|
| o 1 1
|/
o 0 0
$ hg log -r 3 --debug --patch --git --copies
changeset: 3:19cd7d1417952af13161b94c32e901769104560c
tag: tip
phase: draft
parent: 2:b5c505595c9e9a12d5dd457919c143e05fc16fb8
parent: -1:0000000000000000000000000000000000000000
manifest: 3:3d27ce8d02241aa59b60804805edf103c5c0cda4
user: test
date: Thu Jan 01 00:00:00 1970 +0000
extra: branch=default
extra: source=a03df74c41413a75c0a42997fc36c2de97b26658
description:
1
Here, revision 3 is created because there is a copy record for 'b' in the
dirstate and thus 'b' is considered modified. But this information is discarded
at commit time since 'b' content is unchanged. I do not know if discarding this
information is correct or not, but at this time we cannot represent it anyway.
This patch therefore implements the last solution of moving the logic into
dirstate.setparents(). It does not sound crazy as 'm' files makes no sense with
only one parent. It also makes dirstate.merge() calls .lookupnormal() if there
is one parent, to preserve the invariant.
I am a bit concerned about introducing this kind of stateful behaviour to
existing code which historically treated setparents() as a basic setter without
side-effects. And doing that during the code freeze.
2012-04-22 22:06:36 +04:00
|
|
|
oldp2 = self._pl[1]
|
2016-08-11 18:00:41 +03:00
|
|
|
if self._origpl is None:
|
|
|
|
self._origpl = self._pl
|
2017-09-26 13:56:20 +03:00
|
|
|
self._map.setparents(p1, p2)
|
2022-02-10 01:26:09 +03:00
|
|
|
copies: "Dict[str, str]" = {}
|
2018-06-11 23:49:45 +03:00
|
|
|
copymap = self._map.copymap
|
rebase: skip resolved but emptied revisions
When rebasing, if a conflict occurs and is resolved in a way the rebased
revision becomes empty, it is not skipped, unlike revisions being emptied
without conflicts.
The reason is:
- File 'x' is merged and resolved, merge.update() marks it as 'm' in the
dirstate.
- rebase.concludenode() calls localrepo.commit(), which calls
localrepo.status() which calls dirstate.status(). 'x' shows up as 'm' and is
unconditionnally added to the modified files list, instead of being checked
again.
- localrepo.commit() detects 'x' as changed an create a new revision where only
the manifest parents and linkrev differ.
Marking 'x' as modified without checking it makes sense for regular merges. But
in rebase case, the merge looks normal but the second parent is usually
discarded. When this happens, 'm' files in dirstate are a bit irrelevant and
should be considered 'n' possibly dirty instead. That is what the current patch
does.
Another approach, maybe more efficient, would be to pass another flag to
merge.update() saying the 'branchmerge' is a bit of a lie and recordupdate()
should call dirstate.normallookup() instead of merge().
It is also tempting to add this logic to dirstate.setparents(), moving from two
to one parent is what invalidates the 'm' markers. But this is a far bigger
change to make.
v2: succumb to the temptation and move the logic in dirstate.setparents(). mpm
suggested trying _filecommit() first but it is called by commitctx() which
knows nothing about the dirstate and comes too late into the game. A second
approach was to rewrite the 'm' state into 'n' on the fly in dirstate.status()
which failed for graft in the following case:
$ hg init repo
$ cd repo
$ echo a > a
$ hg ci -qAm0
$ echo a >> a
$ hg ci -m1
$ hg up 0
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg mv a b
$ echo c > b
$ hg ci -m2
created new head
$ hg graft 1 --tool internal:local
grafting revision 1
$ hg --config extensions.graphlog= glog --template '{rev} {desc|firstline}\n'
@ 3 1
|
o 2 2
|
| o 1 1
|/
o 0 0
$ hg log -r 3 --debug --patch --git --copies
changeset: 3:19cd7d1417952af13161b94c32e901769104560c
tag: tip
phase: draft
parent: 2:b5c505595c9e9a12d5dd457919c143e05fc16fb8
parent: -1:0000000000000000000000000000000000000000
manifest: 3:3d27ce8d02241aa59b60804805edf103c5c0cda4
user: test
date: Thu Jan 01 00:00:00 1970 +0000
extra: branch=default
extra: source=a03df74c41413a75c0a42997fc36c2de97b26658
description:
1
Here, revision 3 is created because there is a copy record for 'b' in the
dirstate and thus 'b' is considered modified. But this information is discarded
at commit time since 'b' content is unchanged. I do not know if discarding this
information is correct or not, but at this time we cannot represent it anyway.
This patch therefore implements the last solution of moving the logic into
dirstate.setparents(). It does not sound crazy as 'm' files makes no sense with
only one parent. It also makes dirstate.merge() calls .lookupnormal() if there
is one parent, to preserve the invariant.
I am a bit concerned about introducing this kind of stateful behaviour to
existing code which historically treated setparents() as a basic setter without
side-effects. And doing that during the code freeze.
2012-04-22 22:06:36 +04:00
|
|
|
if oldp2 != nullid and p2 == nullid:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
candidatefiles = self._map.nonnormalset.union(self._map.otherparentset)
|
2017-03-09 04:35:20 +03:00
|
|
|
for f in candidatefiles:
|
|
|
|
s = self._map.get(f)
|
|
|
|
if s is None:
|
|
|
|
continue
|
|
|
|
|
2014-10-10 22:05:50 +04:00
|
|
|
# Discard 'm' markers when moving away from a merge state
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if s[0] == "m":
|
2018-06-11 23:49:45 +03:00
|
|
|
source = copymap.get(f)
|
2017-08-23 21:24:57 +03:00
|
|
|
if source:
|
|
|
|
copies[f] = source
|
rebase: skip resolved but emptied revisions
When rebasing, if a conflict occurs and is resolved in a way the rebased
revision becomes empty, it is not skipped, unlike revisions being emptied
without conflicts.
The reason is:
- File 'x' is merged and resolved, merge.update() marks it as 'm' in the
dirstate.
- rebase.concludenode() calls localrepo.commit(), which calls
localrepo.status() which calls dirstate.status(). 'x' shows up as 'm' and is
unconditionnally added to the modified files list, instead of being checked
again.
- localrepo.commit() detects 'x' as changed an create a new revision where only
the manifest parents and linkrev differ.
Marking 'x' as modified without checking it makes sense for regular merges. But
in rebase case, the merge looks normal but the second parent is usually
discarded. When this happens, 'm' files in dirstate are a bit irrelevant and
should be considered 'n' possibly dirty instead. That is what the current patch
does.
Another approach, maybe more efficient, would be to pass another flag to
merge.update() saying the 'branchmerge' is a bit of a lie and recordupdate()
should call dirstate.normallookup() instead of merge().
It is also tempting to add this logic to dirstate.setparents(), moving from two
to one parent is what invalidates the 'm' markers. But this is a far bigger
change to make.
v2: succumb to the temptation and move the logic in dirstate.setparents(). mpm
suggested trying _filecommit() first but it is called by commitctx() which
knows nothing about the dirstate and comes too late into the game. A second
approach was to rewrite the 'm' state into 'n' on the fly in dirstate.status()
which failed for graft in the following case:
$ hg init repo
$ cd repo
$ echo a > a
$ hg ci -qAm0
$ echo a >> a
$ hg ci -m1
$ hg up 0
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg mv a b
$ echo c > b
$ hg ci -m2
created new head
$ hg graft 1 --tool internal:local
grafting revision 1
$ hg --config extensions.graphlog= glog --template '{rev} {desc|firstline}\n'
@ 3 1
|
o 2 2
|
| o 1 1
|/
o 0 0
$ hg log -r 3 --debug --patch --git --copies
changeset: 3:19cd7d1417952af13161b94c32e901769104560c
tag: tip
phase: draft
parent: 2:b5c505595c9e9a12d5dd457919c143e05fc16fb8
parent: -1:0000000000000000000000000000000000000000
manifest: 3:3d27ce8d02241aa59b60804805edf103c5c0cda4
user: test
date: Thu Jan 01 00:00:00 1970 +0000
extra: branch=default
extra: source=a03df74c41413a75c0a42997fc36c2de97b26658
description:
1
Here, revision 3 is created because there is a copy record for 'b' in the
dirstate and thus 'b' is considered modified. But this information is discarded
at commit time since 'b' content is unchanged. I do not know if discarding this
information is correct or not, but at this time we cannot represent it anyway.
This patch therefore implements the last solution of moving the logic into
dirstate.setparents(). It does not sound crazy as 'm' files makes no sense with
only one parent. It also makes dirstate.merge() calls .lookupnormal() if there
is one parent, to preserve the invariant.
I am a bit concerned about introducing this kind of stateful behaviour to
existing code which historically treated setparents() as a basic setter without
side-effects. And doing that during the code freeze.
2012-04-22 22:06:36 +04:00
|
|
|
self.normallookup(f)
|
2014-10-10 22:05:50 +04:00
|
|
|
# Also fix up otherparent markers
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
elif s[0] == "n" and s[2] == -2:
|
2018-06-11 23:49:45 +03:00
|
|
|
source = copymap.get(f)
|
2017-08-23 21:24:57 +03:00
|
|
|
if source:
|
|
|
|
copies[f] = source
|
2014-10-10 22:05:50 +04:00
|
|
|
self.add(f)
|
2012-04-30 00:25:55 +04:00
|
|
|
return copies
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def setbranch(self, branch: str) -> None:
|
2020-01-29 18:38:41 +03:00
|
|
|
assert isinstance(branch, str)
|
2010-11-25 00:56:32 +03:00
|
|
|
self._branch = encoding.fromlocal(branch)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
f = self._opener("branch", "w", atomictemp=True, checkambig=True)
|
2012-04-19 19:11:42 +04:00
|
|
|
try:
|
2020-01-29 18:38:41 +03:00
|
|
|
f.write(encodeutf8(self._branch + "\n"))
|
2012-04-19 19:11:42 +04:00
|
|
|
f.close()
|
2012-12-16 22:33:00 +04:00
|
|
|
|
|
|
|
# make sure filecache has the correct stat info for _branch after
|
|
|
|
# replacing the underlying file
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
ce = self._filecache["_branch"]
|
2012-12-16 22:33:00 +04:00
|
|
|
if ce:
|
|
|
|
ce.refresh()
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
except: # re-raises
|
2022-05-05 05:32:11 +03:00
|
|
|
# pyre-fixme[16]: `BinaryIO` has no attribute `discard`.
|
2012-12-15 22:19:07 +04:00
|
|
|
f.discard()
|
|
|
|
raise
|
2007-03-14 02:50:02 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def invalidate(self) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Causes the next access to reread the dirstate.
|
2017-06-05 02:08:50 +03:00
|
|
|
|
|
|
|
This is different from localrepo.invalidatedirstate() because it always
|
|
|
|
rereads the dirstate. Use localrepo.invalidatedirstate() if you want to
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
check whether the dirstate has changed before rereading it."""
|
2017-06-05 02:08:50 +03:00
|
|
|
|
2017-10-05 21:34:41 +03:00
|
|
|
for a in ("_map", "_branch", "_ignore"):
|
2007-07-20 02:43:25 +04:00
|
|
|
if a in self.__dict__:
|
|
|
|
delattr(self, a)
|
2012-01-08 21:15:54 +04:00
|
|
|
self._lastnormaltime = 0
|
2007-07-22 01:02:09 +04:00
|
|
|
self._dirty = False
|
2017-03-06 03:20:07 +03:00
|
|
|
self._updatedfiles.clear()
|
2014-09-05 22:34:29 +04:00
|
|
|
self._parentwriters = 0
|
2016-08-11 18:00:41 +03:00
|
|
|
self._origpl = None
|
2007-04-24 23:02:51 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def copy(self, source: str, dest: str) -> None:
|
2009-12-28 01:24:05 +03:00
|
|
|
"""Mark dest as a copy of source. Unmark dest if source is None."""
|
2008-06-15 15:01:03 +04:00
|
|
|
if source == dest:
|
|
|
|
return
|
2007-07-22 01:02:09 +04:00
|
|
|
self._dirty = True
|
2018-06-11 23:49:45 +03:00
|
|
|
if self._istreestate:
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, self._map)
|
|
|
|
tsmap.copy(source, dest)
|
2018-06-11 23:49:45 +03:00
|
|
|
# treestatemap.copymap needs to be changed via the "copy" method.
|
|
|
|
# _updatedfiles is not used by treestatemap as it's tracked
|
|
|
|
# internally.
|
|
|
|
return
|
2020-08-12 07:43:21 +03:00
|
|
|
dmap = cast(Union[dirstatemap, treedirstate.treedirstatemap], self._map)
|
2009-01-04 23:32:40 +03:00
|
|
|
if source is not None:
|
2020-08-12 07:43:21 +03:00
|
|
|
dmap.copymap[dest] = source
|
2017-03-06 03:20:07 +03:00
|
|
|
self._updatedfiles.add(source)
|
|
|
|
self._updatedfiles.add(dest)
|
2020-08-12 07:43:21 +03:00
|
|
|
elif dmap.copymap.pop(dest, None):
|
2017-03-06 03:20:07 +03:00
|
|
|
self._updatedfiles.add(dest)
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def copied(self, file: str) -> "Optional[str]":
|
2018-06-25 23:55:57 +03:00
|
|
|
if self._istreestate:
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, self._map)
|
|
|
|
return tsmap.copysource(file)
|
2018-06-25 23:55:57 +03:00
|
|
|
else:
|
2020-08-12 07:43:21 +03:00
|
|
|
dmap = cast(Union[dirstatemap, treedirstate.treedirstatemap], self._map)
|
|
|
|
return dmap.copymap.get(file, None)
|
2006-09-26 02:53:17 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def copies(self) -> "Dict[str, str]":
|
2017-09-26 13:56:20 +03:00
|
|
|
return self._map.copymap
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def needcheck(self, file: str) -> bool:
|
2018-06-15 07:23:07 +03:00
|
|
|
"""Mark file as need-check"""
|
|
|
|
if not self._istreestate:
|
|
|
|
raise error.ProgrammingError("needcheck is only supported by treestate")
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, self._map)
|
|
|
|
changed = tsmap.needcheck(file)
|
2018-06-15 07:23:07 +03:00
|
|
|
self._dirty |= changed
|
|
|
|
return changed
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def clearneedcheck(self, file: str) -> None:
|
2018-10-30 06:03:50 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
raise error.ProgrammingError("needcheck is only supported by treestate")
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, self._map)
|
|
|
|
changed = tsmap.clearneedcheck(file)
|
2018-10-30 06:03:50 +03:00
|
|
|
self._dirty |= changed
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def setclock(self, clock: str) -> None:
|
2018-06-15 07:23:07 +03:00
|
|
|
"""Set fsmonitor clock"""
|
2018-11-03 21:10:56 +03:00
|
|
|
return self.setmeta("clock", clock)
|
2018-06-15 07:23:07 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def getclock(self) -> "Optional[str]":
|
2018-06-15 07:23:07 +03:00
|
|
|
"""Get fsmonitor clock"""
|
2018-11-03 21:10:56 +03:00
|
|
|
return self.getmeta("clock")
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def setmeta(self, name: str, value: "Optional[str]") -> None:
|
2018-11-03 21:10:56 +03:00
|
|
|
"""Set metadata"""
|
|
|
|
if not self._istreestate:
|
|
|
|
raise error.ProgrammingError("setmeta is only supported by treestate")
|
|
|
|
value = value or None
|
|
|
|
if value != self.getmeta(name):
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, self._map)
|
|
|
|
tsmap.updatemetadata({name: value})
|
2018-11-03 21:10:56 +03:00
|
|
|
self._dirty = True
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def getmeta(self, name: str) -> "Optional[str]":
|
2018-11-03 21:10:56 +03:00
|
|
|
"""Get metadata"""
|
2018-06-15 07:23:07 +03:00
|
|
|
if not self._istreestate:
|
2018-11-03 21:10:56 +03:00
|
|
|
raise error.ProgrammingError("getmeta is only supported by treestate")
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, self._map)
|
2018-11-03 21:10:56 +03:00
|
|
|
# Normalize "" to "None"
|
2020-08-12 07:43:21 +03:00
|
|
|
return tsmap.getmetadata().get(name) or None
|
2018-06-15 07:23:07 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _addpath(self, f: str, state: str, mode: int, size: int, mtime: int) -> None:
|
2007-11-05 20:05:44 +03:00
|
|
|
oldstate = self[f]
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if state == "a" or oldstate == "r":
|
2011-04-21 15:18:52 +04:00
|
|
|
scmutil.checkfilename(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
if self._map.hastrackeddir(f):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
raise error.Abort(_("directory %r already in dirstate") % f)
|
2020-07-08 06:30:39 +03:00
|
|
|
if os.path.isabs(f):
|
2020-07-20 23:26:26 +03:00
|
|
|
raise error.Abort(
|
|
|
|
_("cannot add non-root-relative path to dirstate: %s") % f
|
|
|
|
)
|
2020-08-28 19:39:34 +03:00
|
|
|
relativedirs = [".", ".."]
|
|
|
|
if any(s for s in f.split("/") if s in relativedirs):
|
|
|
|
raise error.Abort(_("cannot add path with relative parents: %s") % f)
|
|
|
|
|
2008-07-12 03:46:02 +04:00
|
|
|
# shadows
|
2015-04-07 00:36:08 +03:00
|
|
|
for d in util.finddirs(f):
|
2017-11-15 12:07:42 +03:00
|
|
|
if self._map.hastrackeddir(d):
|
2008-07-12 03:46:02 +04:00
|
|
|
break
|
2017-09-14 19:41:22 +03:00
|
|
|
entry = self._map.get(d)
|
2018-07-17 20:44:53 +03:00
|
|
|
if entry is not None and entry[0] not in "r?":
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
raise error.Abort(_("file %r in dirstate clashes with %r") % (d, f))
|
2012-06-18 19:06:42 +04:00
|
|
|
self._dirty = True
|
2017-03-06 03:20:07 +03:00
|
|
|
self._updatedfiles.add(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
self._map.addfile(f, oldstate, state, mode, size, mtime)
|
2007-11-05 20:05:44 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def normal(self, f: str) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Mark a file normal and clean."""
|
2019-12-10 00:09:25 +03:00
|
|
|
s = util.lstat(self._join(f))
|
2015-11-19 22:15:17 +03:00
|
|
|
mtime = s.st_mtime
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._addpath(f, "n", s.st_mode, s.st_size & _rangemask, mtime & _rangemask)
|
2018-06-11 23:49:45 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
self._map.copymap.pop(f, None)
|
2018-06-18 23:53:08 +03:00
|
|
|
if f in self._map.nonnormalset:
|
|
|
|
self._map.nonnormalset.remove(f)
|
2011-03-25 17:03:53 +03:00
|
|
|
if mtime > self._lastnormaltime:
|
|
|
|
# Remember the most recent modification timeslot for status(),
|
2011-03-24 20:39:54 +03:00
|
|
|
# to make sure we won't miss future size-preserving file content
|
|
|
|
# modifications that happen within the same timeslot.
|
2011-03-25 17:03:53 +03:00
|
|
|
self._lastnormaltime = mtime
|
dirstate: avoid a race with multiple commits in the same process
(issue2264, issue2516)
The race happens when two commits in a row change the same file
without changing its size, *if* those two commits happen in the same
second in the same process while holding the same repo lock. For
example:
commit 1:
M a
M b
commit 2: # same process, same second, same repo lock
M b # modify b without changing its size
M c
This first manifested in transplant, which is the most common way to
do multiple commits in the same process. But it can manifest in any
script or extension that does multiple commits under the same repo
lock. (Thus, the test script tests both transplant and a custom script.)
The problem was that dirstate.status() failed to notice the change to
b when localrepo is about to do the second commit, meaning that change
gets left in the working directory. In the context of transplant, that
means either a crash ("RuntimeError: nothing committed after
transplant") or a silently inaccurate transplant, depending on whether
any other files were modified by the second transplanted changeset.
The fix is to make status() work a little harder when we have
previously marked files as clean (state 'normal') in the same process.
Specifically, dirstate.normal() adds files to self._lastnormal, and
other state-changing methods remove them. Then dirstate.status() puts
any files in self._lastnormal into state 'lookup', which will make
localrepository.status() read file contents to see if it has really
changed. So we pay a small performance penalty for the second (and
subsequent) commits in the same process, without affecting the common
case. Anything that does lots of status updates and checks in the
same process could suffer a performance hit.
Incidentally, there is a simpler fix: call dirstate.normallookup() on
every file updated by commit() at the end of the commit. The trouble
with that solution is that it imposes a performance penalty on the
common case: it means the next status-dependent hg command after every
"hg commit" will be a little bit slower. The patch here is more
complex, but only affects performance for the uncommon case.
2011-03-21 00:41:09 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def normallookup(self, f: str) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Mark a file normal, but possibly dirty."""
|
2017-09-14 19:41:22 +03:00
|
|
|
if self._pl[1] != nullid:
|
2008-03-18 10:07:39 +03:00
|
|
|
# if there is a merge going on and the file was either
|
2010-04-20 13:17:01 +04:00
|
|
|
# in state 'm' (-1) or coming from other parent (-2) before
|
|
|
|
# being removed, restore that state.
|
2017-09-14 19:41:22 +03:00
|
|
|
entry = self._map.get(f)
|
|
|
|
if entry is not None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if entry[0] == "r" and entry[2] in (-1, -2):
|
2017-09-26 13:56:20 +03:00
|
|
|
source = self._map.copymap.get(f)
|
2017-09-14 19:41:22 +03:00
|
|
|
if entry[2] == -1:
|
|
|
|
self.merge(f)
|
|
|
|
elif entry[2] == -2:
|
|
|
|
self.otherparent(f)
|
|
|
|
if source:
|
|
|
|
self.copy(source, f)
|
|
|
|
return
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if entry[0] == "m" or entry[0] == "n" and entry[2] == -2:
|
2017-09-14 19:41:22 +03:00
|
|
|
return
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._addpath(f, "n", 0, -1, -1)
|
2018-06-11 23:49:45 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
self._map.copymap.pop(f, None)
|
merge: forcefully mark files that we get from the second parent as dirty
After a hg merge, we want to include in the commit all the files that we
got from the second parent, so that we have the correct file-level
history. To make them visible to hg commit, we try to mark them as dirty.
Unfortunately, right now we can't really mark them as dirty[1] - the
best we can do is to mark them as needing a full comparison of their
contents, but they will still be considered clean if they happen to be
identical to the version in the first parent.
This changeset extends the dirstate format in a compatible way, so that
we can mark a file as dirty:
Right now we use a negative file size to indicate we don't have valid
stat data for this entry. In practice, this size is always -1.
This patch uses -2 to indicate that the entry is dirty. Older versions
of hg won't choke on this dirstate, but they may happily mark the file
as clean after a full comparison, destroying all of our hard work.
The patch adds a dirstate.normallookup method with the semantics of the
current normaldirty, and changes normaldirty to forcefully mark the
entry as dirty.
This should fix issue522.
[1] - well, we could put them in state 'm', but that state has a
different meaning.
2007-08-23 08:48:29 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def otherparent(self, f: str) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Mark as coming from the other parent, always dirty."""
|
2010-04-20 13:17:01 +04:00
|
|
|
if self._pl[1] == nullid:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
raise error.Abort(
|
|
|
|
_("setting %r to other parent " "only allowed in merges") % f
|
|
|
|
)
|
|
|
|
if f in self and self[f] == "n":
|
2014-10-10 22:31:06 +04:00
|
|
|
# merge-like
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._addpath(f, "m", 0, -2, -1)
|
2014-10-10 22:31:06 +04:00
|
|
|
else:
|
|
|
|
# add-like
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._addpath(f, "n", 0, -2, -1)
|
2018-06-11 23:49:45 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
self._map.copymap.pop(f, None)
|
2007-07-22 01:02:09 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def add(self, f: str) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Mark a file added."""
|
|
|
|
self._addpath(f, "a", 0, -1, -1)
|
2018-06-11 23:49:45 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
self._map.copymap.pop(f, None)
|
2007-07-22 01:02:09 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def remove(self, f: str) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Mark a file removed."""
|
2007-07-22 01:02:09 +04:00
|
|
|
self._dirty = True
|
2017-11-15 12:07:42 +03:00
|
|
|
oldstate = self[f]
|
2008-03-18 10:07:39 +03:00
|
|
|
size = 0
|
2017-09-14 19:41:22 +03:00
|
|
|
if self._pl[1] != nullid:
|
|
|
|
entry = self._map.get(f)
|
|
|
|
if entry is not None:
|
|
|
|
# backup the previous state
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if entry[0] == "m": # merge
|
2017-09-14 19:41:22 +03:00
|
|
|
size = -1
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
elif entry[0] == "n" and entry[2] == -2: # other parent
|
2017-09-14 19:41:22 +03:00
|
|
|
size = -2
|
2018-06-18 23:53:08 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
self._map.otherparentset.add(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
self._updatedfiles.add(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
self._map.removefile(f, oldstate, size)
|
2018-06-11 23:49:45 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
if size == 0:
|
|
|
|
self._map.copymap.pop(f, None)
|
2007-07-22 01:02:09 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def merge(self, f: str) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Mark a file merged."""
|
rebase: skip resolved but emptied revisions
When rebasing, if a conflict occurs and is resolved in a way the rebased
revision becomes empty, it is not skipped, unlike revisions being emptied
without conflicts.
The reason is:
- File 'x' is merged and resolved, merge.update() marks it as 'm' in the
dirstate.
- rebase.concludenode() calls localrepo.commit(), which calls
localrepo.status() which calls dirstate.status(). 'x' shows up as 'm' and is
unconditionnally added to the modified files list, instead of being checked
again.
- localrepo.commit() detects 'x' as changed an create a new revision where only
the manifest parents and linkrev differ.
Marking 'x' as modified without checking it makes sense for regular merges. But
in rebase case, the merge looks normal but the second parent is usually
discarded. When this happens, 'm' files in dirstate are a bit irrelevant and
should be considered 'n' possibly dirty instead. That is what the current patch
does.
Another approach, maybe more efficient, would be to pass another flag to
merge.update() saying the 'branchmerge' is a bit of a lie and recordupdate()
should call dirstate.normallookup() instead of merge().
It is also tempting to add this logic to dirstate.setparents(), moving from two
to one parent is what invalidates the 'm' markers. But this is a far bigger
change to make.
v2: succumb to the temptation and move the logic in dirstate.setparents(). mpm
suggested trying _filecommit() first but it is called by commitctx() which
knows nothing about the dirstate and comes too late into the game. A second
approach was to rewrite the 'm' state into 'n' on the fly in dirstate.status()
which failed for graft in the following case:
$ hg init repo
$ cd repo
$ echo a > a
$ hg ci -qAm0
$ echo a >> a
$ hg ci -m1
$ hg up 0
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
$ hg mv a b
$ echo c > b
$ hg ci -m2
created new head
$ hg graft 1 --tool internal:local
grafting revision 1
$ hg --config extensions.graphlog= glog --template '{rev} {desc|firstline}\n'
@ 3 1
|
o 2 2
|
| o 1 1
|/
o 0 0
$ hg log -r 3 --debug --patch --git --copies
changeset: 3:19cd7d1417952af13161b94c32e901769104560c
tag: tip
phase: draft
parent: 2:b5c505595c9e9a12d5dd457919c143e05fc16fb8
parent: -1:0000000000000000000000000000000000000000
manifest: 3:3d27ce8d02241aa59b60804805edf103c5c0cda4
user: test
date: Thu Jan 01 00:00:00 1970 +0000
extra: branch=default
extra: source=a03df74c41413a75c0a42997fc36c2de97b26658
description:
1
Here, revision 3 is created because there is a copy record for 'b' in the
dirstate and thus 'b' is considered modified. But this information is discarded
at commit time since 'b' content is unchanged. I do not know if discarding this
information is correct or not, but at this time we cannot represent it anyway.
This patch therefore implements the last solution of moving the logic into
dirstate.setparents(). It does not sound crazy as 'm' files makes no sense with
only one parent. It also makes dirstate.merge() calls .lookupnormal() if there
is one parent, to preserve the invariant.
I am a bit concerned about introducing this kind of stateful behaviour to
existing code which historically treated setparents() as a basic setter without
side-effects. And doing that during the code freeze.
2012-04-22 22:06:36 +04:00
|
|
|
if self._pl[1] == nullid:
|
|
|
|
return self.normallookup(f)
|
2014-10-11 23:05:09 +04:00
|
|
|
return self.otherparent(f)
|
2007-07-22 01:02:09 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def untrack(self, f: str) -> None:
|
2018-10-12 19:35:04 +03:00
|
|
|
"""Stops tracking a file in the dirstate. This is useful during
|
|
|
|
operations that want to stop tracking a file, but still have it show up
|
|
|
|
as untracked (like hg forget)."""
|
2017-11-15 12:07:42 +03:00
|
|
|
oldstate = self[f]
|
2018-10-12 19:35:04 +03:00
|
|
|
if self._map.untrackfile(f, oldstate):
|
2011-11-02 00:19:37 +04:00
|
|
|
self._dirty = True
|
2018-06-11 23:49:45 +03:00
|
|
|
if not self._istreestate:
|
|
|
|
self._updatedfiles.add(f)
|
|
|
|
self._map.copymap.pop(f, None)
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def delete(self, f: str) -> None:
|
2018-10-12 19:35:08 +03:00
|
|
|
"""Removes a file from the dirstate entirely. This is useful during
|
|
|
|
operations like update, to remove files from the dirstate that are known
|
|
|
|
to be deleted."""
|
|
|
|
oldstate = self[f]
|
|
|
|
if self._map.deletefile(f, oldstate):
|
|
|
|
self._dirty = True
|
|
|
|
if not self._istreestate:
|
|
|
|
self._updatedfiles.add(f)
|
|
|
|
self._map.copymap.pop(f, None)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _discoverpath(
|
|
|
|
self,
|
|
|
|
path: str,
|
|
|
|
normed: str,
|
|
|
|
ignoremissing: bool,
|
|
|
|
exists: "Optional[bool]",
|
|
|
|
storemap: "Dict[str, str]",
|
|
|
|
) -> str:
|
2015-03-30 05:23:05 +03:00
|
|
|
if exists is None:
|
|
|
|
exists = os.path.lexists(os.path.join(self._root, path))
|
|
|
|
if not exists:
|
|
|
|
# Maybe a path component exists
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if not ignoremissing and "/" in path:
|
|
|
|
d, f = path.rsplit("/", 1)
|
2015-03-30 05:23:05 +03:00
|
|
|
d = self._normalize(d, False, ignoremissing, None)
|
|
|
|
folded = d + "/" + f
|
|
|
|
else:
|
|
|
|
# No path components, preserve original case
|
|
|
|
folded = path
|
|
|
|
else:
|
|
|
|
# recursively normalize leading directory components
|
|
|
|
# against dirstate
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if "/" in normed:
|
|
|
|
d, f = normed.rsplit("/", 1)
|
2015-03-30 05:23:05 +03:00
|
|
|
d = self._normalize(d, False, ignoremissing, True)
|
|
|
|
r = self._root + "/" + d
|
|
|
|
folded = d + "/" + util.fspath(f, r)
|
|
|
|
else:
|
|
|
|
folded = util.fspath(normed, self._root)
|
|
|
|
storemap[normed] = folded
|
|
|
|
|
|
|
|
return folded
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _normalizefile(
|
|
|
|
self,
|
|
|
|
path: str,
|
|
|
|
isknown: bool,
|
|
|
|
ignoremissing: bool = False,
|
|
|
|
exists: "Optional[bool]" = None,
|
|
|
|
) -> str:
|
2015-03-29 04:53:54 +03:00
|
|
|
normed = util.normcase(path)
|
2017-10-05 21:34:41 +03:00
|
|
|
folded = self._map.filefoldmap.get(normed, None)
|
2015-03-29 04:53:54 +03:00
|
|
|
if folded is None:
|
|
|
|
if isknown:
|
|
|
|
folded = path
|
|
|
|
else:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
folded = self._discoverpath(
|
|
|
|
path, normed, ignoremissing, exists, self._map.filefoldmap
|
|
|
|
)
|
2015-03-29 04:53:54 +03:00
|
|
|
return folded
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _normalize(
|
|
|
|
self,
|
|
|
|
path: str,
|
|
|
|
isknown: bool,
|
|
|
|
ignoremissing: bool = False,
|
|
|
|
exists: "Optional[bool]" = None,
|
|
|
|
) -> str:
|
2011-11-16 00:25:11 +04:00
|
|
|
normed = util.normcase(path)
|
2017-10-05 21:34:41 +03:00
|
|
|
folded = self._map.filefoldmap.get(normed, None)
|
2015-04-01 05:34:37 +03:00
|
|
|
if folded is None:
|
2017-10-05 21:34:41 +03:00
|
|
|
folded = self._map.dirfoldmap.get(normed, None)
|
2011-03-22 19:59:43 +03:00
|
|
|
if folded is None:
|
2012-04-28 22:29:21 +04:00
|
|
|
if isknown:
|
2011-03-22 19:59:43 +03:00
|
|
|
folded = path
|
2008-10-01 01:23:08 +04:00
|
|
|
else:
|
2015-03-30 05:42:49 +03:00
|
|
|
# store discovered result in dirfoldmap so that future
|
|
|
|
# normalizefile calls don't start matching directories
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
folded = self._discoverpath(
|
|
|
|
path, normed, ignoremissing, exists, self._map.dirfoldmap
|
|
|
|
)
|
2011-03-22 19:59:43 +03:00
|
|
|
return folded
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def normalize(
|
|
|
|
self, path: str, isknown: bool = False, ignoremissing: bool = False
|
|
|
|
) -> str:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2011-03-22 19:59:43 +03:00
|
|
|
normalize the case of a pathname when on a casefolding filesystem
|
|
|
|
|
|
|
|
isknown specifies whether the filename came from walking the
|
2012-04-28 22:29:21 +04:00
|
|
|
disk, to avoid extra filesystem access.
|
|
|
|
|
|
|
|
If ignoremissing is True, missing path are returned
|
|
|
|
unchanged. Otherwise, we try harder to normalize possibly
|
|
|
|
existing path components.
|
2011-03-22 19:59:43 +03:00
|
|
|
|
|
|
|
The normalized case is determined based on the following precedence:
|
|
|
|
|
|
|
|
- version of name already stored in the dirstate
|
|
|
|
- version of name stored on disk
|
|
|
|
- version provided via command arguments
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2011-03-22 19:59:43 +03:00
|
|
|
|
|
|
|
if self._checkcase:
|
2012-04-28 22:29:21 +04:00
|
|
|
return self._normalize(path, isknown, ignoremissing)
|
2011-03-22 19:59:43 +03:00
|
|
|
return path
|
2008-06-06 22:23:29 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def clear(self) -> None:
|
2017-10-27 02:15:31 +03:00
|
|
|
self._map.clear()
|
2012-01-08 21:15:54 +04:00
|
|
|
self._lastnormaltime = 0
|
2017-03-06 03:20:07 +03:00
|
|
|
self._updatedfiles.clear()
|
2007-08-06 08:00:10 +04:00
|
|
|
self._dirty = True
|
2007-08-06 06:04:56 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def rebuild(
|
|
|
|
self,
|
|
|
|
parent: bytes,
|
|
|
|
allfiles: "Sequence[str]",
|
|
|
|
changedfiles: "Optional[Sequence[str]]" = None,
|
|
|
|
exact: bool = False,
|
|
|
|
) -> None:
|
2018-05-03 03:08:29 +03:00
|
|
|
# If exact is True, then assume only changedfiles can be changed, and
|
|
|
|
# other files cannot be possibly changed. This is used by "absorb" as
|
|
|
|
# a hint to perform a fast path for fsmonitor and sparse.
|
2015-06-05 08:10:32 +03:00
|
|
|
if changedfiles is None:
|
2018-05-03 03:08:29 +03:00
|
|
|
if exact:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
raise error.ProgrammingError("exact requires changedfiles")
|
2015-11-30 22:23:15 +03:00
|
|
|
# Rebuild entire dirstate
|
2015-06-05 08:10:32 +03:00
|
|
|
changedfiles = allfiles
|
2015-11-30 22:23:15 +03:00
|
|
|
lastnormaltime = self._lastnormaltime
|
|
|
|
self.clear()
|
|
|
|
self._lastnormaltime = lastnormaltime
|
|
|
|
|
2016-08-31 01:16:28 +03:00
|
|
|
if self._origpl is None:
|
|
|
|
self._origpl = self._pl
|
2017-09-26 13:56:20 +03:00
|
|
|
self._map.setparents(parent, nullid)
|
2015-11-30 22:23:15 +03:00
|
|
|
for f in changedfiles:
|
|
|
|
if f in allfiles:
|
2016-08-31 01:16:28 +03:00
|
|
|
self.normallookup(f)
|
2006-02-20 21:04:56 +03:00
|
|
|
else:
|
2018-10-12 19:35:04 +03:00
|
|
|
self.untrack(f)
|
2015-11-30 22:23:15 +03:00
|
|
|
|
2007-07-22 01:02:09 +04:00
|
|
|
self._dirty = True
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def identity(self) -> object:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Return identity of dirstate itself to detect changing in storage
|
2017-06-09 07:07:48 +03:00
|
|
|
|
|
|
|
If identity of previous dirstate is equal to this, writing
|
|
|
|
changes based on the former dirstate out can keep consistency.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2017-10-05 21:34:41 +03:00
|
|
|
return self._map.identity
|
2017-06-09 07:07:48 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def write(self, tr: "Optional[transaction.transaction]") -> None:
|
2007-06-18 22:24:34 +04:00
|
|
|
if not self._dirty:
|
2006-02-23 04:17:08 +03:00
|
|
|
return
|
2014-07-22 18:59:30 +04:00
|
|
|
|
2015-10-13 20:49:17 +03:00
|
|
|
filename = self._filename
|
2016-08-02 17:51:27 +03:00
|
|
|
if tr:
|
2020-01-15 04:45:49 +03:00
|
|
|
self._markforwrite()
|
2015-10-13 20:49:17 +03:00
|
|
|
return
|
|
|
|
|
2016-06-02 18:44:20 +03:00
|
|
|
st = self._opener(filename, "w", atomictemp=True, checkambig=True)
|
2015-10-07 19:41:30 +03:00
|
|
|
self._writedirstate(st)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _markforwrite(self) -> None:
|
2020-01-15 04:45:49 +03:00
|
|
|
tr = self._repo.currenttransaction()
|
|
|
|
if not tr:
|
|
|
|
raise error.ProgrammingError("no transaction during dirstate write")
|
|
|
|
|
|
|
|
self._dirty = True
|
|
|
|
|
|
|
|
# 'dirstate.write()' is not only for writing in-memory
|
|
|
|
# changes out, but also for dropping ambiguous timestamp.
|
|
|
|
# delayed writing re-raise "ambiguous timestamp issue".
|
|
|
|
# See also the wiki page below for detail:
|
|
|
|
# https://www.mercurial-scm.org/wiki/DirstateTransactionPlan
|
|
|
|
|
|
|
|
# emulate dropping timestamp in 'parsers.pack_dirstate'
|
|
|
|
now = _getfsnow(self._opener)
|
|
|
|
self._map.clearambiguoustimes(self._updatedfiles, now)
|
|
|
|
|
|
|
|
# emulate that all 'dirstate.normal' results are written out
|
|
|
|
self._lastnormaltime = 0
|
|
|
|
self._updatedfiles.clear()
|
|
|
|
|
|
|
|
# delay writing in-memory changes out
|
|
|
|
tr.addfilegenerator(
|
|
|
|
"dirstate", (self._filename,), self._writedirstate, location="local"
|
|
|
|
)
|
|
|
|
|
2019-04-04 21:23:56 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def checkoutidentifier(self) -> str:
|
2019-04-04 21:23:56 +03:00
|
|
|
try:
|
2020-01-29 18:38:41 +03:00
|
|
|
return self._opener.readutf8("checkoutidentifier")
|
2019-04-04 21:23:56 +03:00
|
|
|
except IOError as e:
|
|
|
|
if e.errno != errno.ENOENT:
|
|
|
|
raise
|
|
|
|
return ""
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def addparentchangecallback(
|
|
|
|
self, category: str, callback: "ParentChangeCallback"
|
|
|
|
) -> None:
|
2016-08-11 18:00:41 +03:00
|
|
|
"""add a callback to be called when the wd parents are changed
|
|
|
|
|
|
|
|
Callback will be called with the following arguments:
|
|
|
|
dirstate, (oldp1, oldp2), (newp1, newp2)
|
|
|
|
|
|
|
|
Category is a unique identifier to allow overwriting an old callback
|
|
|
|
with a newer callback.
|
|
|
|
"""
|
|
|
|
self._plchangecallbacks[category] = callback
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _writedirstate(self, st: "BinaryIO") -> None:
|
2016-08-11 18:00:41 +03:00
|
|
|
# notify callbacks about parents change
|
2020-08-12 07:43:21 +03:00
|
|
|
origpl = self._origpl
|
|
|
|
if origpl is not None and origpl != self._pl:
|
2020-01-29 03:25:29 +03:00
|
|
|
for c, callback in sorted(pycompat.iteritems(self._plchangecallbacks)):
|
2020-08-12 07:43:21 +03:00
|
|
|
callback(self, origpl, self._pl)
|
2019-04-04 21:23:56 +03:00
|
|
|
# if the first parent has changed then consider this a new checkout
|
2020-08-12 07:43:21 +03:00
|
|
|
if origpl[0] != self._pl[0]:
|
2019-04-04 21:23:56 +03:00
|
|
|
with self._opener("checkoutidentifier", "w", atomictemp=True) as f:
|
2020-01-29 18:38:41 +03:00
|
|
|
f.write(util.makerandomidentifier().encode("utf-8"))
|
2019-04-04 21:23:56 +03:00
|
|
|
util.clearcachedproperty(self, "checkoutidentifier")
|
2016-08-11 18:00:41 +03:00
|
|
|
self._origpl = None
|
2009-10-01 19:17:52 +04:00
|
|
|
# use the modification time of the newly created temporary file as the
|
|
|
|
# filesystem's notion of 'now'
|
2015-11-19 22:15:17 +03:00
|
|
|
now = util.fstat(st).st_mtime & _rangemask
|
2015-12-17 05:46:53 +03:00
|
|
|
|
|
|
|
# enough 'delaywrite' prevents 'pack_dirstate' from dropping
|
|
|
|
# timestamp of each entries in dirstate, because of 'now > mtime'
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
delaywrite = self._ui.configint("debug", "dirstate.delaywrite")
|
2015-12-17 05:46:53 +03:00
|
|
|
if delaywrite > 0:
|
2015-12-17 05:49:18 +03:00
|
|
|
# do we have any files to delay for?
|
2020-01-29 03:25:29 +03:00
|
|
|
for f, e in pycompat.iteritems(self._map):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if e[0] == "n" and e[3] == now:
|
|
|
|
import time # to avoid useless import
|
|
|
|
|
2015-12-17 05:58:26 +03:00
|
|
|
# rather than sleep n seconds, sleep until the next
|
|
|
|
# multiple of n seconds
|
|
|
|
clock = time.time()
|
|
|
|
start = int(clock) - (int(clock) % delaywrite)
|
|
|
|
end = start + delaywrite
|
|
|
|
time.sleep(end - clock)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
now = end # trust our estimate that the end is near now
|
2015-12-17 05:49:18 +03:00
|
|
|
break
|
2015-12-17 05:46:53 +03:00
|
|
|
|
2017-10-05 21:34:41 +03:00
|
|
|
self._map.write(st, now)
|
2013-04-28 01:19:52 +04:00
|
|
|
self._lastnormaltime = 0
|
2017-10-05 21:34:41 +03:00
|
|
|
self._dirty = False
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _dirignore(self, f: str) -> bool:
|
2019-08-15 01:44:17 +03:00
|
|
|
if f == "":
|
2008-04-05 20:15:04 +04:00
|
|
|
return False
|
dirstate: stop testing directories as files in ignore handling
Summary:
This is subtle.
`.hgignore`'s current behavior: if `^foo$` rule exists, then directory `foo/`
is ignored (ex. 'foo/bar' should be ignored).
However, that imposes problems for the sparse ignore matcher, which is the
"negate" of the "include" matcher. A user can write `[include]` glob patterns
like:
a*{b*,c*/d*}/e*
The ignore matcher will be the negate of the above patterns. Then because
`a1b2` does not match `a*{b*,c*/d*}/e`, the negate matcher returns "True",
and the ignore matcher will ignore the directory. So even if file `a1b2/e3`
should be selected, the parent directory being ignored cause the file to
be ignored.
That is clearly incorrect for sparse's usecase.
I think the issue is fundementally a layer violation - it's the *matcher*'s
responsibility to check whether one of the parent directory is matched (or
ignored), not the directory walker's responsibility.
This diff fixes the walker so it uses the visitdir interface, and moves back
the directory check to hgignore matcher to maintain compatibility. For three
matchers involved in ignore handling:
- hgignore matcher: updated to do the recursive directory handling on its own
- gitignore matcher: work out of box. already consider parent directories!
- sparse matcher: want the new behavior
`test-sparse-issues.t` is now green.
With this change, the `forceincludematcher` subdir hack used in sparse is no
longer necessary. Therefore removed.
Besides, all ignore matchers can handle "visitdir" correctly. That is, if
`visitdir('x')` returns `'all'`, then `visitdir('x/y')` will also return `'all'`.
Therefore the parent directory logic in `dirstate.dirignore` becomes
unnecessary and dropped.
Reviewed By: DurhamG
Differential Revision: D10861612
fbshipit-source-id: aa0c181ae64b361b85f08b8fecfdfe6331e9a4c2
2018-12-13 09:42:17 +03:00
|
|
|
visitdir = self._ignore.visitdir
|
|
|
|
if visitdir(f) == "all":
|
2008-02-08 23:07:55 +03:00
|
|
|
return True
|
|
|
|
return False
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _ignorefiles(self) -> "List[str]":
|
2015-12-23 22:52:54 +03:00
|
|
|
files = []
|
2019-04-30 04:19:49 +03:00
|
|
|
files += self._globalignorefiles()
|
2018-08-03 06:18:50 +03:00
|
|
|
return files
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _globalignorefiles(self) -> "List[str]":
|
2018-08-03 06:18:50 +03:00
|
|
|
files = []
|
2015-12-23 22:52:54 +03:00
|
|
|
for name, path in self._ui.configitems("ui"):
|
2018-08-03 06:18:50 +03:00
|
|
|
# A path could have an optional prefix (ex. "git:") to select file
|
|
|
|
# format
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if name == "ignore" or name.startswith("ignore."):
|
2015-12-23 22:52:54 +03:00
|
|
|
# we need to use os.path.join here rather than self._join
|
|
|
|
# because path is arbitrary and user-specified
|
2018-08-03 06:18:50 +03:00
|
|
|
fullpath = os.path.join(self._rootdir, util.expandpath(path))
|
2019-04-30 04:19:49 +03:00
|
|
|
files.append(fullpath)
|
2015-12-23 22:52:54 +03:00
|
|
|
return files
|
|
|
|
|
2022-07-01 03:33:09 +03:00
|
|
|
class FallbackToPythonStatus(Exception):
|
|
|
|
pass
|
|
|
|
|
|
|
|
def _ruststatus(
|
|
|
|
self, match: "Callable[[str], bool]", ignored: bool, clean: bool, unknown: bool
|
|
|
|
) -> "scmutil.status":
|
2022-07-14 00:09:54 +03:00
|
|
|
if util.safehasattr(self._fs, "_fsmonitorstate"):
|
|
|
|
filesystem = "watchman"
|
|
|
|
elif "eden" in self._repo.requirements:
|
|
|
|
filesystem = "eden"
|
|
|
|
else:
|
|
|
|
filesystem = "normal"
|
2022-07-01 03:33:09 +03:00
|
|
|
|
2022-07-14 00:09:54 +03:00
|
|
|
# TODO: Fix deadlock in normal filesystem crawler
|
|
|
|
if ignored or clean or filesystem == "normal":
|
|
|
|
raise self.FallbackToPythonStatus
|
2022-07-01 03:33:09 +03:00
|
|
|
|
2022-07-14 00:09:54 +03:00
|
|
|
if filesystem == "eden":
|
2022-07-01 03:33:09 +03:00
|
|
|
# EdenFS repos still use an old dirstate to track working copy
|
|
|
|
# changes. We need a TreeState for Rust status, so if the map
|
|
|
|
# doesn't have a tree, we create a temporary read-only one.
|
|
|
|
# Note: this TreeState won't track clean files, only added/removed/etc.
|
|
|
|
# TODO: get rid of this when EdenFS migrates to TreeState.
|
|
|
|
tempdir = tempfile.TemporaryDirectory()
|
|
|
|
tempvfs = vfs.vfs(tempdir.name)
|
|
|
|
tempvfs.makedir("treestate")
|
|
|
|
tempmap = treestate.treestatemap(
|
|
|
|
self._ui, tempvfs, tempdir.name, importdirstate=self
|
|
|
|
)
|
|
|
|
tree = tempmap._tree
|
|
|
|
else:
|
|
|
|
# pyre-fixme[16]: Item `dirstatemap` of `Union[dirstatemap,
|
|
|
|
# treedirstatemap, treestatemap]` has no attribute `_tree`.
|
|
|
|
tree = self._map._tree
|
|
|
|
|
2022-07-14 00:09:54 +03:00
|
|
|
# TODO: Handle the case that a file is ignored but is still tracked
|
|
|
|
# in p1.
|
|
|
|
match = matchmod.differencematcher(match, self._ignore)
|
|
|
|
|
2022-07-01 03:33:09 +03:00
|
|
|
return bindings.workingcopy.status.status(
|
|
|
|
self._root,
|
|
|
|
self._repo[self.p1()].manifest(),
|
|
|
|
self._repo.fileslog.filescmstore,
|
|
|
|
tree,
|
|
|
|
self._lastnormaltime,
|
|
|
|
match,
|
|
|
|
unknown,
|
2022-07-14 00:09:54 +03:00
|
|
|
filesystem,
|
2022-07-01 03:33:09 +03:00
|
|
|
)
|
|
|
|
|
2019-03-26 05:22:16 +03:00
|
|
|
@perftrace.tracefunc("Status")
|
2022-02-10 01:26:09 +03:00
|
|
|
def status(
|
|
|
|
self, match: "Callable[[str], bool]", ignored: bool, clean: bool, unknown: bool
|
|
|
|
) -> "scmutil.status":
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Determine the status of the working copy relative to the
|
2022-03-11 00:16:04 +03:00
|
|
|
dirstate and return a scmutil.status.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""
|
2022-03-11 00:16:04 +03:00
|
|
|
if self._ui.configbool("workingcopy", "ruststatus"):
|
2022-07-01 03:33:09 +03:00
|
|
|
try:
|
|
|
|
return self._ruststatus(match, ignored, clean, unknown)
|
|
|
|
except self.FallbackToPythonStatus:
|
|
|
|
pass
|
2022-03-11 00:16:04 +03:00
|
|
|
|
2019-10-02 20:56:15 +03:00
|
|
|
wctx = self._repo[None]
|
|
|
|
# Prime the wctx._parents cache so the parent doesn't change out from
|
|
|
|
# under us if a checkout happens in another process.
|
2021-09-09 02:17:51 +03:00
|
|
|
pctx = wctx.p1()
|
2019-10-02 20:56:15 +03:00
|
|
|
|
2008-06-26 23:35:50 +04:00
|
|
|
listignored, listclean, listunknown = ignored, clean, unknown
|
2022-02-10 01:26:09 +03:00
|
|
|
modified: "List[str]" = []
|
|
|
|
added: "List[str]" = []
|
|
|
|
unknownpaths: "List[str]" = []
|
|
|
|
ignoredpaths: "List[str]" = []
|
|
|
|
removed: "List[str]" = []
|
|
|
|
deleted: "List[str]" = []
|
|
|
|
cleanpaths: "List[str]" = []
|
2005-08-28 01:21:25 +04:00
|
|
|
|
2007-07-26 21:02:58 +04:00
|
|
|
dmap = self._map
|
2017-10-28 22:35:54 +03:00
|
|
|
dmap.preload()
|
|
|
|
dget = dmap.__getitem__
|
2007-07-26 21:02:58 +04:00
|
|
|
madd = modified.append
|
|
|
|
aadd = added.append
|
2020-02-22 00:48:20 +03:00
|
|
|
uadd = unknownpaths.append
|
|
|
|
iadd = ignoredpaths.append
|
2007-07-26 21:02:58 +04:00
|
|
|
radd = removed.append
|
|
|
|
dadd = deleted.append
|
2020-02-22 00:48:20 +03:00
|
|
|
cadd = cleanpaths.append
|
dirstate: stop testing directories as files in ignore handling
Summary:
This is subtle.
`.hgignore`'s current behavior: if `^foo$` rule exists, then directory `foo/`
is ignored (ex. 'foo/bar' should be ignored).
However, that imposes problems for the sparse ignore matcher, which is the
"negate" of the "include" matcher. A user can write `[include]` glob patterns
like:
a*{b*,c*/d*}/e*
The ignore matcher will be the negate of the above patterns. Then because
`a1b2` does not match `a*{b*,c*/d*}/e`, the negate matcher returns "True",
and the ignore matcher will ignore the directory. So even if file `a1b2/e3`
should be selected, the parent directory being ignored cause the file to
be ignored.
That is clearly incorrect for sparse's usecase.
I think the issue is fundementally a layer violation - it's the *matcher*'s
responsibility to check whether one of the parent directory is matched (or
ignored), not the directory walker's responsibility.
This diff fixes the walker so it uses the visitdir interface, and moves back
the directory check to hgignore matcher to maintain compatibility. For three
matchers involved in ignore handling:
- hgignore matcher: updated to do the recursive directory handling on its own
- gitignore matcher: work out of box. already consider parent directories!
- sparse matcher: want the new behavior
`test-sparse-issues.t` is now green.
With this change, the `forceincludematcher` subdir hack used in sparse is no
longer necessary. Therefore removed.
Besides, all ignore matchers can handle "visitdir" correctly. That is, if
`visitdir('x')` returns `'all'`, then `visitdir('x/y')` will also return `'all'`.
Therefore the parent directory logic in `dirstate.dirignore` becomes
unnecessary and dropped.
Reviewed By: DurhamG
Differential Revision: D10861612
fbshipit-source-id: aa0c181ae64b361b85f08b8fecfdfe6331e9a4c2
2018-12-13 09:42:17 +03:00
|
|
|
ignore = self._ignore
|
2017-09-26 13:56:20 +03:00
|
|
|
copymap = self._map.copymap
|
2007-07-26 21:02:58 +04:00
|
|
|
|
2019-02-06 06:36:49 +03:00
|
|
|
# We have seen some rare issues that a few "M" or "R" files show up
|
|
|
|
# while the files are expected to be clean. Log the reason of first few
|
|
|
|
# "M" files.
|
2020-01-28 21:21:58 +03:00
|
|
|
mtolog = self._ui.configint("experimental", "samplestatus") or 0
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
|
2019-10-17 03:38:30 +03:00
|
|
|
oldid = self.identity()
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
|
|
|
|
# Step 1: Get the files that are different from the clean checkedout p1 tree.
|
|
|
|
pendingchanges = self._fs.pendingchanges(match, listignored=listignored)
|
|
|
|
|
2020-01-15 04:45:49 +03:00
|
|
|
for fn, exists in pendingchanges:
|
2020-01-29 18:38:41 +03:00
|
|
|
assert isinstance(fn, str)
|
2018-01-26 18:01:45 +03:00
|
|
|
try:
|
|
|
|
t = dget(fn)
|
2018-06-15 07:23:07 +03:00
|
|
|
# This "?" state is only tracked by treestate, emulate the old
|
|
|
|
# behavior - KeyError.
|
|
|
|
if t[0] == "?":
|
|
|
|
raise KeyError
|
2018-01-26 18:01:45 +03:00
|
|
|
except KeyError:
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
isignored = ignore(fn)
|
|
|
|
if listignored and isignored:
|
|
|
|
iadd(fn)
|
|
|
|
elif listunknown and not isignored:
|
2007-07-26 21:02:58 +04:00
|
|
|
uadd(fn)
|
2005-10-28 00:29:35 +04:00
|
|
|
continue
|
2008-05-12 20:37:08 +04:00
|
|
|
|
2014-05-28 08:02:16 +04:00
|
|
|
state = t[0]
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
if not exists and state in "nma":
|
2008-07-22 22:02:36 +04:00
|
|
|
dadd(fn)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
elif state == "n":
|
2020-01-15 04:45:49 +03:00
|
|
|
madd(fn)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
else:
|
|
|
|
# All other states will be handled by the logic below, and we
|
|
|
|
# don't care that it's a pending change.
|
|
|
|
pass
|
|
|
|
|
2020-01-15 04:45:49 +03:00
|
|
|
# Fetch the nonnormalset after iterating over pendingchanges, since the
|
|
|
|
# iteration may change the nonnormalset as lookup states are resolved.
|
|
|
|
if util.safehasattr(dmap, "nonnormalsetfiltered"):
|
|
|
|
# treestate has a fast path to filter out ignored directories.
|
2022-02-10 01:26:09 +03:00
|
|
|
ignorevisitdir: "Callable[[str], Union[str, bool]]" = ignore.visitdir
|
2020-01-15 04:45:49 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def dirfilter(path: str) -> bool:
|
2020-01-15 04:45:49 +03:00
|
|
|
result = ignorevisitdir(path.rstrip("/"))
|
|
|
|
return result == "all"
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, dmap)
|
|
|
|
nonnormalset = tsmap.nonnormalsetfiltered(dirfilter)
|
2020-01-15 04:45:49 +03:00
|
|
|
else:
|
|
|
|
nonnormalset = dmap.nonnormalset
|
|
|
|
|
|
|
|
otherparentset = dmap.otherparentset
|
|
|
|
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
# The seen set is used to prevent steps 2 and 3 from processing things
|
2020-01-15 04:45:49 +03:00
|
|
|
# we saw in step 1.
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
seenset = set(deleted + modified)
|
|
|
|
|
2019-10-15 06:53:35 +03:00
|
|
|
# audit_path is used to verify that nonnormal files still exist and are
|
|
|
|
# not behind symlinks.
|
2022-02-10 01:26:09 +03:00
|
|
|
auditpath: "pathutil.pathauditor" = pathutil.pathauditor(
|
2020-08-12 07:43:21 +03:00
|
|
|
self._root, cached=True
|
2022-02-10 01:26:09 +03:00
|
|
|
)
|
2019-10-15 06:53:35 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def fileexists(fn: str) -> bool:
|
2019-10-15 06:53:35 +03:00
|
|
|
# So let's double check for the existence of that file.
|
|
|
|
st = list(util.statfiles([self._join(fn)]))[0]
|
|
|
|
|
|
|
|
# auditpath checks to see if the file is under a symlink directory.
|
|
|
|
# If it is, we treat it the same as if it didn't exist.
|
|
|
|
return st is not None and auditpath.check(fn)
|
|
|
|
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
# Step 2: Handle status results that are not simply pending filesystem
|
|
|
|
# changes on top of the pristine tree.
|
|
|
|
for fn in otherparentset:
|
2020-01-29 18:38:41 +03:00
|
|
|
assert isinstance(fn, str)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
if not match(fn) or fn in seenset:
|
|
|
|
continue
|
|
|
|
t = dget(fn)
|
|
|
|
state = t[0]
|
|
|
|
# We only need to handle 'n' here, since all other states will be
|
|
|
|
# covered by the nonnormal loop below.
|
|
|
|
if state in "n":
|
2019-10-15 06:53:35 +03:00
|
|
|
# pendingchanges() above only checks for changes against p1.
|
|
|
|
# For things from p2, we need to manually check for
|
|
|
|
# existence. We don't have to check if they're modified,
|
|
|
|
# since them coming from p2 indicates they are considered
|
|
|
|
# modified.
|
|
|
|
if fileexists(fn):
|
2019-02-06 06:36:49 +03:00
|
|
|
if mtolog > 0:
|
|
|
|
mtolog -= 1
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
self._ui.log("status", "M %s: exists in p2" % fn)
|
|
|
|
madd(fn)
|
2019-10-15 06:53:35 +03:00
|
|
|
else:
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
dadd(fn)
|
|
|
|
seenset.add(fn)
|
|
|
|
|
|
|
|
for fn in nonnormalset:
|
2020-01-29 18:38:41 +03:00
|
|
|
assert isinstance(fn, str)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
if not match(fn) or fn in seenset:
|
|
|
|
continue
|
|
|
|
t = dget(fn)
|
|
|
|
state = t[0]
|
|
|
|
if state == "m":
|
2007-07-26 21:02:58 +04:00
|
|
|
madd(fn)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
seenset.add(fn)
|
2019-02-06 06:36:49 +03:00
|
|
|
if mtolog > 0:
|
|
|
|
mtolog -= 1
|
|
|
|
self._ui.log("status", "M %s: state is 'm' (merge)" % fn)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
elif state == "a":
|
2019-10-15 06:53:35 +03:00
|
|
|
if fileexists(fn):
|
|
|
|
aadd(fn)
|
|
|
|
else:
|
|
|
|
# If an added file is deleted, report it as missing
|
|
|
|
dadd(fn)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
seenset.add(fn)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
elif state == "r":
|
2007-07-26 21:02:58 +04:00
|
|
|
radd(fn)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
seenset.add(fn)
|
|
|
|
elif state == "n":
|
|
|
|
# This can happen if the file is in a lookup state, but all 'n'
|
|
|
|
# files should've been checked in fs.pendingchanges, so we can
|
|
|
|
# ignore it here.
|
|
|
|
pass
|
|
|
|
elif state == "?":
|
|
|
|
# I'm pretty sure this is a bug if nonnormalset contains unknown
|
|
|
|
# files, but the tests say it can happen so let's just ignore
|
|
|
|
# it.
|
|
|
|
pass
|
|
|
|
else:
|
|
|
|
raise error.ProgrammingError(
|
|
|
|
"unexpected nonnormal state '%s' " "for '%s'" % (t, fn)
|
|
|
|
)
|
|
|
|
|
|
|
|
# Most copies should be handled above, as modifies or adds, but there
|
|
|
|
# can be cases where a file is clean and already committed and a commit
|
|
|
|
# is just retroactively marking it as copied. In that case we need to
|
|
|
|
# mark is as modified.
|
|
|
|
for fn in copymap:
|
2020-01-29 18:38:41 +03:00
|
|
|
assert isinstance(fn, str)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
if not match(fn) or fn in seenset:
|
|
|
|
continue
|
|
|
|
# It seems like a bug, but the tests show that copymap can contain
|
|
|
|
# files that aren't in the dirstate. I believe this is caused by
|
|
|
|
# using treestate, which leaves the copymap as partially maintained.
|
|
|
|
if fn not in dmap:
|
|
|
|
continue
|
|
|
|
madd(fn)
|
|
|
|
seenset.add(fn)
|
2005-10-28 00:29:35 +04:00
|
|
|
|
2019-10-02 20:56:15 +03:00
|
|
|
status = scmutil.status(
|
2020-02-22 00:48:20 +03:00
|
|
|
modified, added, removed, deleted, unknownpaths, ignoredpaths, cleanpaths
|
2019-10-02 20:56:15 +03:00
|
|
|
)
|
|
|
|
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
# Step 3: If clean files were requested, add those to the results
|
|
|
|
seenset = set()
|
|
|
|
for files in status:
|
|
|
|
seenset.update(files)
|
|
|
|
seenset.update(util.dirs(files))
|
|
|
|
|
|
|
|
if listclean:
|
|
|
|
for fn in pctx.manifest().matches(match):
|
2020-01-29 18:38:41 +03:00
|
|
|
assert isinstance(fn, str)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
if fn not in seenset:
|
|
|
|
cadd(fn)
|
2020-02-22 00:48:20 +03:00
|
|
|
seenset.update(cleanpaths)
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
|
|
|
|
# Step 4: Report any explicitly requested files that don't exist
|
2020-05-22 05:31:01 +03:00
|
|
|
# pyre-fixme[16]: Anonymous callable has no attribute `files`.
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
for path in sorted(match.files()):
|
|
|
|
try:
|
|
|
|
if path in seenset:
|
|
|
|
continue
|
|
|
|
os.lstat(os.path.join(self._root, path))
|
|
|
|
except OSError as ex:
|
2020-05-22 05:31:01 +03:00
|
|
|
# pyre-fixme[16]: Anonymous callable has no attribute `bad`.
|
filesystem: implement fs.pendingchanges()
Summary:
dirstate.status can be thought of as three stages: 1) checking what
files have changed on disk, 2) adding nonnormal files (added, removed, copied,
merged), and 3) adding clean files. The current implementation ties these
together in one big pile.
As part of refactoring the working copy interface into clear working copy and
filesystem interfaces, this diff extracts the "check what files have changed on
disk" part into the filesystem class.
Note, this implements a walk function very similar to the one that exists in
dirstate. The difference is that dirstate.walk cares about everything that is in
the dirstate already, while the fs walk only cares about what files are
different from the pristine tree, so it's easier to reason about.
Note: This diff does not update the fsmonitor or eden dirstate implementations.
That means those tests will break if I land this. I'm going to send two more diffs
to update their implementations, then I'll be sure to land them all at once.
Future cleanup:
- lookup resolution should be done inside the filesystem layer, since it's an
artifact of filesystem limitations.
- I'd like to get rid of ignore file special casing and have that just be part
of the matcher that is passed in. This might not be feasible though.
- I'd like to get rid of explicit file special casing and have the caller handle
that if needed.
- I'd like to remove the ability to list clean files in status. Most callers
don't need that capability, and a caller could compute that themselves if
needed.
Reviewed By: quark-zju
Differential Revision: D17099990
fbshipit-source-id: d7530e26f057d8fd38aaa36512fa398a543b23c2
2019-10-09 02:43:10 +03:00
|
|
|
match.bad(path, encoding.strtolocal(ex.strerror))
|
|
|
|
|
2020-01-15 04:45:49 +03:00
|
|
|
# TODO: fire this inside filesystem. fixup is a list of files that
|
|
|
|
# checklookup says are clean
|
2019-10-02 20:56:15 +03:00
|
|
|
if not getattr(self._repo, "_insidepoststatusfixup", False):
|
2020-01-15 04:45:49 +03:00
|
|
|
self._poststatusfixup(status, wctx, oldid)
|
2019-10-02 20:56:15 +03:00
|
|
|
|
2019-03-26 05:22:16 +03:00
|
|
|
perftrace.tracevalue("A/M/R Files", len(modified) + len(added) + len(removed))
|
2020-02-22 00:48:20 +03:00
|
|
|
if len(unknownpaths) > 0:
|
|
|
|
perftrace.tracevalue("Unknown Files", len(unknownpaths))
|
|
|
|
if len(ignoredpaths) > 0:
|
|
|
|
perftrace.tracevalue("Ignored Files", len(ignoredpaths))
|
2019-10-02 20:56:15 +03:00
|
|
|
return status
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _poststatusfixup(
|
|
|
|
self, status: "scmutil.status", wctx: "context.workingctx", oldid: object
|
|
|
|
) -> None:
|
2019-10-02 20:56:15 +03:00
|
|
|
"""update dirstate for files that are actually clean"""
|
|
|
|
poststatusbefore = self._repo.postdsstatus(afterdirstatewrite=False)
|
|
|
|
poststatusafter = self._repo.postdsstatus(afterdirstatewrite=True)
|
|
|
|
ui = self._repo.ui
|
2020-01-15 04:45:49 +03:00
|
|
|
if poststatusbefore or poststatusafter or self._dirty:
|
2019-10-02 20:56:15 +03:00
|
|
|
# prevent infinite loop because fsmonitor postfixup might call
|
|
|
|
# wctx.status()
|
2020-08-12 07:43:21 +03:00
|
|
|
# pyre-fixme[16]: localrepo has no attribute _insidepoststatusfixup
|
2019-10-02 20:56:15 +03:00
|
|
|
self._repo._insidepoststatusfixup = True
|
|
|
|
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. This is a bit weird because we're inside the
|
|
|
|
# dirstate that is no longer valid.
|
|
|
|
|
|
|
|
# If watchman reports fresh instance, still take the lock,
|
|
|
|
# since not updating watchman state leads to very painful
|
|
|
|
# performance.
|
|
|
|
freshinstance = False
|
2021-01-13 03:23:59 +03:00
|
|
|
nonnormalcount = 0
|
2019-10-02 20:56:15 +03:00
|
|
|
try:
|
2020-08-12 07:43:21 +03:00
|
|
|
# pyre-fixme[16]: physicalfilesystem has no attr _fsmonitorstate
|
2019-10-09 02:43:10 +03:00
|
|
|
freshinstance = self._fs._fsmonitorstate._lastisfresh
|
2021-01-13 03:23:59 +03:00
|
|
|
nonnormalcount = self._fs._fsmonitorstate._lastnonnormalcount
|
2019-10-02 20:56:15 +03:00
|
|
|
except Exception:
|
|
|
|
pass
|
2021-01-13 03:23:59 +03:00
|
|
|
waitforlock = False
|
|
|
|
nonnormalthreshold = self._repo.ui.configint(
|
|
|
|
"fsmonitor", "dirstate-nonnormal-file-threshold"
|
|
|
|
)
|
|
|
|
if (
|
|
|
|
nonnormalthreshold is not None
|
|
|
|
and nonnormalcount >= nonnormalthreshold
|
|
|
|
):
|
|
|
|
ui.debug(
|
|
|
|
"poststatusfixup decides to wait for wlock since nonnormal file count %s >= %s\n"
|
|
|
|
% (nonnormalcount, nonnormalthreshold)
|
|
|
|
)
|
|
|
|
waitforlock = True
|
2019-10-02 20:56:15 +03:00
|
|
|
if freshinstance:
|
2021-01-13 03:23:59 +03:00
|
|
|
waitforlock = True
|
2019-10-02 20:56:15 +03:00
|
|
|
ui.debug(
|
|
|
|
"poststatusfixup decides to wait for wlock since watchman reported fresh instance\n"
|
|
|
|
)
|
|
|
|
|
2021-01-13 03:23:59 +03:00
|
|
|
with self._repo.disableeventreporting(), self._repo.wlock(waitforlock):
|
2020-01-15 04:45:49 +03:00
|
|
|
identity = self._repo.dirstate.identity()
|
2020-01-15 04:45:49 +03:00
|
|
|
if identity == oldid:
|
2019-10-02 20:56:15 +03:00
|
|
|
if poststatusbefore:
|
|
|
|
for ps in poststatusbefore:
|
|
|
|
ps(wctx, status)
|
|
|
|
|
|
|
|
# write changes out explicitly, because nesting
|
|
|
|
# wlock at runtime may prevent 'wlock.release()'
|
|
|
|
# after this block from doing so for subsequent
|
|
|
|
# changing files
|
|
|
|
#
|
|
|
|
# This is a no-op if dirstate is not dirty.
|
|
|
|
tr = self._repo.currenttransaction()
|
|
|
|
self.write(tr)
|
|
|
|
|
|
|
|
if poststatusafter:
|
|
|
|
for ps in poststatusafter:
|
|
|
|
ps(wctx, status)
|
2021-01-13 03:23:59 +03:00
|
|
|
elif not util.istest():
|
|
|
|
# Too noisy in tests.
|
|
|
|
ui.debug(
|
|
|
|
"poststatusfixup did not write dirstate because identity changed %s != %s\n"
|
|
|
|
% (oldid, identity)
|
|
|
|
)
|
|
|
|
|
|
|
|
except error.LockError as ex:
|
2021-06-29 22:27:53 +03:00
|
|
|
# pyre-fixme[61]: `waitforlock` may not be initialized here.
|
2021-01-13 03:23:59 +03:00
|
|
|
if waitforlock:
|
2019-10-02 20:56:15 +03:00
|
|
|
ui.write_err(
|
|
|
|
_(
|
2021-01-13 03:23:59 +03:00
|
|
|
"warning: failed to update watchman state because wlock cannot be obtained (%s)\n"
|
2019-10-02 20:56:15 +03:00
|
|
|
)
|
2021-01-13 03:23:59 +03:00
|
|
|
% (ex,)
|
2019-10-02 20:56:15 +03:00
|
|
|
)
|
|
|
|
ui.write_err(slowstatuswarning)
|
2021-01-13 03:23:59 +03:00
|
|
|
else:
|
|
|
|
ui.debug(
|
|
|
|
"poststatusfixup did not write dirstate because wlock cannot be obtained (%s)\n"
|
|
|
|
% (ex,)
|
|
|
|
)
|
|
|
|
|
2019-10-02 20:56:15 +03:00
|
|
|
finally:
|
|
|
|
# Even if the wlock couldn't be grabbed, clear out the list.
|
|
|
|
self._repo.clearpostdsstatus()
|
|
|
|
self._repo._insidepoststatusfixup = False
|
2014-08-02 09:05:16 +04:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def matches(self, match: "matchmod.basematcher") -> "Iterable[str]":
|
2019-11-04 22:06:13 +03:00
|
|
|
"""
|
|
|
|
return files in the dirstate (in whatever state) filtered by match
|
|
|
|
"""
|
|
|
|
dmap = self._map
|
|
|
|
if match.always():
|
|
|
|
return dmap.keys()
|
|
|
|
files = match.files()
|
|
|
|
if match.isexact():
|
|
|
|
# fast path -- filter the other way around, since typically files is
|
|
|
|
# much smaller than dmap
|
|
|
|
return [f for f in files if f in dmap]
|
|
|
|
if match.prefix():
|
|
|
|
if self._istreestate:
|
|
|
|
# treestate has a fast path to get files inside a subdirectory.
|
|
|
|
# files are prefixes
|
2020-08-12 07:43:21 +03:00
|
|
|
tsmap = cast(treestate.treestatemap, dmap)
|
2019-11-04 22:06:13 +03:00
|
|
|
result = set()
|
|
|
|
fastpathvalid = True
|
|
|
|
for prefix in files:
|
2020-08-12 07:43:21 +03:00
|
|
|
if prefix in tsmap:
|
2019-11-04 22:06:13 +03:00
|
|
|
# prefix is a file
|
|
|
|
result.add(prefix)
|
2020-08-12 07:43:21 +03:00
|
|
|
elif tsmap.hastrackeddir(prefix + "/"):
|
2019-11-04 22:06:13 +03:00
|
|
|
# prefix is a directory
|
2020-08-12 07:43:21 +03:00
|
|
|
result.update(tsmap.keys(prefix=prefix + "/"))
|
2019-11-04 22:06:13 +03:00
|
|
|
else:
|
|
|
|
# unknown pattern (ex. "."), fast path is invalid
|
|
|
|
fastpathvalid = False
|
|
|
|
break
|
|
|
|
if fastpathvalid:
|
|
|
|
return sorted(result)
|
|
|
|
else:
|
|
|
|
# fast path -- all the values are known to be files, so just
|
|
|
|
# return that
|
|
|
|
if all(fn in dmap for fn in files):
|
|
|
|
return list(files)
|
2021-11-18 10:49:14 +03:00
|
|
|
elif self._istreestate:
|
|
|
|
# Treestate native path. Avoid visiting directories.
|
2022-05-05 05:32:11 +03:00
|
|
|
# pyre-fixme[16]: Item `dirstatemap` of `Union[dirstatemap,
|
|
|
|
# treedirstatemap, treestatemap]` has no attribute `matches`.
|
2021-11-18 10:49:14 +03:00
|
|
|
return dmap.matches(match)
|
|
|
|
# Slow path: scan all files in dirstate.
|
2019-11-04 22:06:13 +03:00
|
|
|
return [f for f in dmap if match(f)]
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _actualfilename(self, tr: "Optional[transaction.transaction]") -> str:
|
2015-10-16 19:15:33 +03:00
|
|
|
if tr:
|
dirstate: make functions for backup aware of transaction activity
Some comments in this patch assume that subsequent patch changes
'dirstate.write()' like as below:
def write(self, repo):
if not self._dirty:
return
tr = repo.currenttransaction()
if tr:
tr.addfilegenerator('dirstate', (self._filename,),
self._writedirstate, location='plain')
return # omit actual writing out
st = self._opener('dirstate', "w", atomictemp=True)
self._writedirstate(st)
This patch makes '_savebackup()' write in-memory changes out, and it
causes clearing 'self._dirty'. If dirstate isn't changed after
'_savebackup()', subsequent 'dirstate.write()' never invokes
'tr.addfilegenerator()' because 'not self._dirty' is true.
Then, 'tr.writepending()' unintentionally returns False, if there is
no other (e.g. changelog) changes pending, even though dirstate
changes are already written out at '_savebackup()'.
To avoid such situation, this patch makes '_savebackup()' explicitly
invoke 'tr.addfilegenerator()', if transaction is running.
'_savebackup()' should get awareness of transaction before 'write()',
because the former depends on the behavior of the latter before this
patch.
2015-10-13 20:49:17 +03:00
|
|
|
return self._pendingfilename
|
|
|
|
else:
|
|
|
|
return self._filename
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def savebackup(
|
|
|
|
self, tr: "Optional[transaction.transaction]", backupname: str
|
|
|
|
) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Save current dirstate into backup file"""
|
2015-10-16 19:15:33 +03:00
|
|
|
filename = self._actualfilename(tr)
|
2017-07-13 01:24:07 +03:00
|
|
|
assert backupname != filename
|
dirstate: make functions for backup aware of transaction activity
Some comments in this patch assume that subsequent patch changes
'dirstate.write()' like as below:
def write(self, repo):
if not self._dirty:
return
tr = repo.currenttransaction()
if tr:
tr.addfilegenerator('dirstate', (self._filename,),
self._writedirstate, location='plain')
return # omit actual writing out
st = self._opener('dirstate', "w", atomictemp=True)
self._writedirstate(st)
This patch makes '_savebackup()' write in-memory changes out, and it
causes clearing 'self._dirty'. If dirstate isn't changed after
'_savebackup()', subsequent 'dirstate.write()' never invokes
'tr.addfilegenerator()' because 'not self._dirty' is true.
Then, 'tr.writepending()' unintentionally returns False, if there is
no other (e.g. changelog) changes pending, even though dirstate
changes are already written out at '_savebackup()'.
To avoid such situation, this patch makes '_savebackup()' explicitly
invoke 'tr.addfilegenerator()', if transaction is running.
'_savebackup()' should get awareness of transaction before 'write()',
because the former depends on the behavior of the latter before this
patch.
2015-10-13 20:49:17 +03:00
|
|
|
|
|
|
|
# use '_writedirstate' instead of 'write' to write changes certainly,
|
|
|
|
# because the latter omits writing out if transaction is running.
|
|
|
|
# output file will be used to create backup of dirstate at this point.
|
2017-03-02 05:21:06 +03:00
|
|
|
if self._dirty or not self._opener.exists(filename):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._writedirstate(
|
|
|
|
self._opener(filename, "w", atomictemp=True, checkambig=True)
|
|
|
|
)
|
dirstate: make functions for backup aware of transaction activity
Some comments in this patch assume that subsequent patch changes
'dirstate.write()' like as below:
def write(self, repo):
if not self._dirty:
return
tr = repo.currenttransaction()
if tr:
tr.addfilegenerator('dirstate', (self._filename,),
self._writedirstate, location='plain')
return # omit actual writing out
st = self._opener('dirstate', "w", atomictemp=True)
self._writedirstate(st)
This patch makes '_savebackup()' write in-memory changes out, and it
causes clearing 'self._dirty'. If dirstate isn't changed after
'_savebackup()', subsequent 'dirstate.write()' never invokes
'tr.addfilegenerator()' because 'not self._dirty' is true.
Then, 'tr.writepending()' unintentionally returns False, if there is
no other (e.g. changelog) changes pending, even though dirstate
changes are already written out at '_savebackup()'.
To avoid such situation, this patch makes '_savebackup()' explicitly
invoke 'tr.addfilegenerator()', if transaction is running.
'_savebackup()' should get awareness of transaction before 'write()',
because the former depends on the behavior of the latter before this
patch.
2015-10-13 20:49:17 +03:00
|
|
|
|
|
|
|
if tr:
|
|
|
|
# ensure that subsequent tr.writepending returns True for
|
|
|
|
# changes written out above, even if dirstate is never
|
|
|
|
# changed after this
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
tr.addfilegenerator(
|
2018-09-28 17:08:40 +03:00
|
|
|
"dirstate", (self._filename,), self._writedirstate, location="local"
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
)
|
dirstate: make functions for backup aware of transaction activity
Some comments in this patch assume that subsequent patch changes
'dirstate.write()' like as below:
def write(self, repo):
if not self._dirty:
return
tr = repo.currenttransaction()
if tr:
tr.addfilegenerator('dirstate', (self._filename,),
self._writedirstate, location='plain')
return # omit actual writing out
st = self._opener('dirstate', "w", atomictemp=True)
self._writedirstate(st)
This patch makes '_savebackup()' write in-memory changes out, and it
causes clearing 'self._dirty'. If dirstate isn't changed after
'_savebackup()', subsequent 'dirstate.write()' never invokes
'tr.addfilegenerator()' because 'not self._dirty' is true.
Then, 'tr.writepending()' unintentionally returns False, if there is
no other (e.g. changelog) changes pending, even though dirstate
changes are already written out at '_savebackup()'.
To avoid such situation, this patch makes '_savebackup()' explicitly
invoke 'tr.addfilegenerator()', if transaction is running.
'_savebackup()' should get awareness of transaction before 'write()',
because the former depends on the behavior of the latter before this
patch.
2015-10-13 20:49:17 +03:00
|
|
|
|
|
|
|
# ensure that pending file written above is unlinked at
|
|
|
|
# failure, even if tr.writepending isn't invoked until the
|
|
|
|
# end of this transaction
|
2018-09-28 17:08:40 +03:00
|
|
|
tr.registertmp(filename, location="local")
|
dirstate: make functions for backup aware of transaction activity
Some comments in this patch assume that subsequent patch changes
'dirstate.write()' like as below:
def write(self, repo):
if not self._dirty:
return
tr = repo.currenttransaction()
if tr:
tr.addfilegenerator('dirstate', (self._filename,),
self._writedirstate, location='plain')
return # omit actual writing out
st = self._opener('dirstate', "w", atomictemp=True)
self._writedirstate(st)
This patch makes '_savebackup()' write in-memory changes out, and it
causes clearing 'self._dirty'. If dirstate isn't changed after
'_savebackup()', subsequent 'dirstate.write()' never invokes
'tr.addfilegenerator()' because 'not self._dirty' is true.
Then, 'tr.writepending()' unintentionally returns False, if there is
no other (e.g. changelog) changes pending, even though dirstate
changes are already written out at '_savebackup()'.
To avoid such situation, this patch makes '_savebackup()' explicitly
invoke 'tr.addfilegenerator()', if transaction is running.
'_savebackup()' should get awareness of transaction before 'write()',
because the former depends on the behavior of the latter before this
patch.
2015-10-13 20:49:17 +03:00
|
|
|
|
2017-03-21 16:50:28 +03:00
|
|
|
self._opener.tryunlink(backupname)
|
2017-03-02 04:59:21 +03:00
|
|
|
# hardlink backup is okay because _writedirstate is always called
|
|
|
|
# with an "atomictemp=True" file.
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
util.copyfile(
|
|
|
|
self._opener.join(filename), self._opener.join(backupname), hardlink=True
|
|
|
|
)
|
2015-10-13 20:49:17 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def restorebackup(
|
|
|
|
self, tr: "Optional[transaction.transaction]", backupname: str
|
|
|
|
) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Restore dirstate by backup file"""
|
2015-10-13 20:49:17 +03:00
|
|
|
# this "invalidate()" prevents "wlock.release()" from writing
|
|
|
|
# changes of dirstate out after restoring from backup file
|
|
|
|
self.invalidate()
|
2015-10-16 19:15:33 +03:00
|
|
|
filename = self._actualfilename(tr)
|
2017-10-20 15:53:35 +03:00
|
|
|
o = self._opener
|
|
|
|
if util.samefile(o.join(backupname), o.join(filename)):
|
|
|
|
o.unlink(backupname)
|
|
|
|
else:
|
|
|
|
o.rename(backupname, filename, checkambig=True)
|
2017-07-13 01:24:07 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def clearbackup(
|
|
|
|
self, tr: "Optional[transaction.transaction]", backupname: str
|
|
|
|
) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Clear backup file"""
|
2017-07-13 01:24:07 +03:00
|
|
|
self._opener.unlink(backupname)
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def loginfo(self, ui: "ui_mod.ui", prefix: str) -> None:
|
2019-04-04 21:23:55 +03:00
|
|
|
try:
|
|
|
|
parents = [hex(p) if p != nullid else "" for p in self._pl]
|
|
|
|
except Exception:
|
|
|
|
# The dirstate may be too corrupt to read. We don't want to fail
|
|
|
|
# just because of logging, so log the parents as unknown.
|
|
|
|
parents = ("unknown", "unknown")
|
2019-04-04 21:23:56 +03:00
|
|
|
data = {
|
|
|
|
prefix + "checkoutidentifier": self.checkoutidentifier,
|
|
|
|
prefix + "wdirparent1": parents[0],
|
|
|
|
prefix + "wdirparent2": parents[1],
|
|
|
|
}
|
2019-04-23 12:45:38 +03:00
|
|
|
ui.log("dirstate_info", **data)
|
2019-04-04 21:23:55 +03:00
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
|
2017-09-26 13:56:20 +03:00
|
|
|
class dirstatemap(object):
|
2017-11-15 12:07:42 +03:00
|
|
|
"""Map encapsulating the dirstate's contents.
|
|
|
|
|
|
|
|
The dirstate contains the following state:
|
|
|
|
|
|
|
|
- `identity` is the identity of the dirstate file, which can be used to
|
|
|
|
detect when changes have occurred to the dirstate file.
|
|
|
|
|
|
|
|
- `parents` is a pair containing the parents of the working copy. The
|
|
|
|
parents are updated by calling `setparents`.
|
|
|
|
|
|
|
|
- the state map maps filenames to tuples of (state, mode, size, mtime),
|
|
|
|
where state is a single character representing 'normal', 'added',
|
2017-11-15 12:07:42 +03:00
|
|
|
'removed', or 'merged'. It is read by treating the dirstate as a
|
|
|
|
dict. File state is updated by calling the `addfile`, `removefile` and
|
2018-10-12 19:35:04 +03:00
|
|
|
`untrackfile` methods.
|
2017-11-15 12:07:42 +03:00
|
|
|
|
|
|
|
- `copymap` maps destination filenames to their source filename.
|
|
|
|
|
|
|
|
The dirstate also provides the following views onto the state:
|
|
|
|
|
|
|
|
- `nonnormalset` is a set of the filenames that have state other
|
|
|
|
than 'normal', or are normal but have an mtime of -1 ('normallookup').
|
|
|
|
|
|
|
|
- `otherparentset` is a set of the filenames that are marked as coming
|
|
|
|
from the second parent when the dirstate is currently being merged.
|
|
|
|
|
|
|
|
- `filefoldmap` is a dict mapping normalized filenames to the denormalized
|
|
|
|
form that they appear as in the dirstate.
|
|
|
|
|
|
|
|
- `dirfoldmap` is a dict mapping normalized directory names to the
|
|
|
|
denormalized form that they appear as in the dirstate.
|
|
|
|
"""
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __init__(self, ui: "ui_mod.ui", opener: "vfs.abstractvfs", root: str) -> None:
|
2017-09-26 13:56:20 +03:00
|
|
|
self._ui = ui
|
|
|
|
self._opener = opener
|
|
|
|
self._root = root
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._filename = "dirstate"
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
self._parents: "Optional[Tuple[bytes, bytes]]" = None
|
2017-09-26 13:56:20 +03:00
|
|
|
self._dirtyparents = False
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2017-09-26 13:56:20 +03:00
|
|
|
# for consistent view between _pl() and _read() invocations
|
2022-02-10 01:26:09 +03:00
|
|
|
self._pendingmode: "Optional[bool]" = None
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def _map(self) -> "Dict[str, dirstatetuple]":
|
2017-10-27 02:15:36 +03:00
|
|
|
self._map = {}
|
|
|
|
self.read()
|
|
|
|
return self._map
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def copymap(self) -> "Dict[str, str]":
|
2017-10-27 02:15:36 +03:00
|
|
|
self.copymap = {}
|
|
|
|
self._map
|
|
|
|
return self.copymap
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def clear(self) -> None:
|
2017-10-28 22:35:54 +03:00
|
|
|
self._map.clear()
|
|
|
|
self.copymap.clear()
|
2017-10-27 02:15:31 +03:00
|
|
|
self.setparents(nullid, nullid)
|
2017-11-15 12:07:42 +03:00
|
|
|
util.clearcachedproperty(self, "_dirs")
|
|
|
|
util.clearcachedproperty(self, "_alldirs")
|
2017-11-08 20:23:53 +03:00
|
|
|
util.clearcachedproperty(self, "filefoldmap")
|
|
|
|
util.clearcachedproperty(self, "dirfoldmap")
|
|
|
|
util.clearcachedproperty(self, "nonnormalset")
|
|
|
|
util.clearcachedproperty(self, "otherparentset")
|
2017-10-27 02:15:31 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def iteritems(self) -> "Iterable[Tuple[str, dirstatetuple]]":
|
2020-01-29 03:25:29 +03:00
|
|
|
return pycompat.iteritems(self._map)
|
2020-02-28 22:29:36 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def items(self) -> "Iterable[Tuple[str, dirstatetuple]]":
|
2020-02-28 22:29:36 +03:00
|
|
|
return pycompat.iteritems(self._map)
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __len__(self) -> int:
|
2017-10-01 18:46:02 +03:00
|
|
|
return len(self._map)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __iter__(self) -> "Iterable[str]":
|
2017-09-26 13:56:20 +03:00
|
|
|
return iter(self._map)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def get(
|
|
|
|
self, key: str, default: "Optional[dirstatetuple]" = None
|
|
|
|
) -> "Optional[dirstatetuple]":
|
2017-09-26 13:56:20 +03:00
|
|
|
return self._map.get(key, default)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __contains__(self, key: str) -> bool:
|
2017-09-26 13:56:20 +03:00
|
|
|
return key in self._map
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def __getitem__(self, key: str) -> "dirstatetuple":
|
2017-09-26 13:56:20 +03:00
|
|
|
return self._map[key]
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def keys(self) -> "Iterable[str]":
|
2017-09-26 13:56:20 +03:00
|
|
|
return self._map.keys()
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def preload(self) -> None:
|
2017-10-28 22:35:54 +03:00
|
|
|
"""Loads the underlying data, if it's not already loaded"""
|
|
|
|
self._map
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def addfile(
|
|
|
|
self, f: str, oldstate: str, state: str, mode: int, size: int, mtime: int
|
|
|
|
) -> None:
|
2017-11-15 12:07:42 +03:00
|
|
|
"""Add a tracked file to the dirstate."""
|
2017-11-15 12:07:42 +03:00
|
|
|
if oldstate in "?r" and "_dirs" in self.__dict__:
|
|
|
|
self._dirs.addpath(f)
|
|
|
|
if oldstate == "?" and "_alldirs" in self.__dict__:
|
|
|
|
self._alldirs.addpath(f)
|
2018-01-03 16:35:56 +03:00
|
|
|
self._insert_tuple(f, state, mode, size, mtime)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if state != "n" or mtime == -1:
|
2017-11-15 12:07:42 +03:00
|
|
|
self.nonnormalset.add(f)
|
|
|
|
if size == -2:
|
|
|
|
self.otherparentset.add(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def removefile(self, f: str, oldstate: str, size: int) -> None:
|
2017-11-15 12:07:42 +03:00
|
|
|
"""
|
|
|
|
Mark a file as removed in the dirstate.
|
|
|
|
|
|
|
|
The `size` parameter is used to store sentinel values that indicate
|
|
|
|
the file's previous state. In the future, we should refactor this
|
|
|
|
to be more explicit about what that state is.
|
|
|
|
"""
|
2017-11-15 12:07:42 +03:00
|
|
|
if oldstate not in "?r" and "_dirs" in self.__dict__:
|
|
|
|
self._dirs.delpath(f)
|
|
|
|
if oldstate == "?" and "_alldirs" in self.__dict__:
|
|
|
|
self._alldirs.addpath(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
if "filefoldmap" in self.__dict__:
|
|
|
|
normed = util.normcase(f)
|
|
|
|
self.filefoldmap.pop(normed, None)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self._insert_tuple(f, "r", 0, size, 0)
|
2017-11-15 12:07:42 +03:00
|
|
|
self.nonnormalset.add(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def deletefile(self, f: str, oldstat: str) -> None:
|
2018-10-12 19:35:08 +03:00
|
|
|
"""
|
|
|
|
Removes a file from the dirstate entirely, implying it doesn't even
|
|
|
|
exist on disk anymore and may not be untracked.
|
|
|
|
"""
|
|
|
|
# In the default dirstate implementation, deletefile is the same as
|
|
|
|
# untrackfile.
|
|
|
|
self.untrackfile(f, oldstat)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def untrackfile(self, f: str, oldstate: str) -> bool:
|
2017-11-15 12:07:42 +03:00
|
|
|
"""
|
2018-10-12 19:35:04 +03:00
|
|
|
Remove a file from the dirstate, leaving it untracked. Returns True if
|
|
|
|
the file was previously recorded.
|
2017-11-15 12:07:42 +03:00
|
|
|
"""
|
2017-11-15 12:07:42 +03:00
|
|
|
exists = self._map.pop(f, None) is not None
|
2017-11-15 12:07:42 +03:00
|
|
|
if exists:
|
2017-11-15 12:07:42 +03:00
|
|
|
if oldstate != "r" and "_dirs" in self.__dict__:
|
|
|
|
self._dirs.delpath(f)
|
|
|
|
if "_alldirs" in self.__dict__:
|
|
|
|
self._alldirs.delpath(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
if "filefoldmap" in self.__dict__:
|
|
|
|
normed = util.normcase(f)
|
|
|
|
self.filefoldmap.pop(normed, None)
|
2017-11-15 12:07:42 +03:00
|
|
|
self.nonnormalset.discard(f)
|
|
|
|
return exists
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def clearambiguoustimes(self, files: "Iterable[str]", now: int) -> None:
|
2017-11-15 12:07:42 +03:00
|
|
|
for f in files:
|
|
|
|
e = self.get(f)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if e is not None and e[0] == "n" and e[3] == now:
|
2018-01-03 16:35:56 +03:00
|
|
|
self._insert_tuple(f, e[0], e[1], e[2], -1)
|
2017-11-15 12:07:42 +03:00
|
|
|
self.nonnormalset.add(f)
|
2017-11-15 12:07:42 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _insert_tuple(
|
|
|
|
self, f: str, state: str, mode: int, size: int, mtime: int
|
|
|
|
) -> None:
|
2018-01-03 16:35:56 +03:00
|
|
|
self._map[f] = dirstatetuple(state, mode, size, mtime)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def nonnormalentries(self) -> "Tuple[Set[str], Set[str]]":
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
"""Compute the nonnormal dirstate entries from the dmap"""
|
2017-09-26 13:56:20 +03:00
|
|
|
try:
|
|
|
|
return parsers.nonnormalotherparententries(self._map)
|
|
|
|
except AttributeError:
|
|
|
|
nonnorm = set()
|
|
|
|
otherparent = set()
|
2020-01-29 03:25:29 +03:00
|
|
|
for fname, e in pycompat.iteritems(self._map):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if e[0] != "n" or e[3] == -1:
|
2017-09-26 13:56:20 +03:00
|
|
|
nonnorm.add(fname)
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if e[0] == "n" and e[2] == -2:
|
2017-09-26 13:56:20 +03:00
|
|
|
otherparent.add(fname)
|
|
|
|
return nonnorm, otherparent
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def filefoldmap(self) -> "Dict[str, str]":
|
2017-09-26 13:56:20 +03:00
|
|
|
"""Returns a dictionary mapping normalized case paths to their
|
|
|
|
non-normalized versions.
|
|
|
|
"""
|
|
|
|
try:
|
|
|
|
makefilefoldmap = parsers.make_file_foldmap
|
|
|
|
except AttributeError:
|
|
|
|
pass
|
|
|
|
else:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
return makefilefoldmap(self._map, util.normcasespec, util.normcasefallback)
|
2017-09-26 13:56:20 +03:00
|
|
|
|
|
|
|
f = {}
|
|
|
|
normcase = util.normcase
|
2020-01-29 03:25:29 +03:00
|
|
|
for name, s in pycompat.iteritems(self._map):
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if s[0] != "r":
|
2017-09-26 13:56:20 +03:00
|
|
|
f[normcase(name)] = name
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
f["."] = "." # prevents useless util.fspath() invocation
|
2017-09-26 13:56:20 +03:00
|
|
|
return f
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def hastrackeddir(self, d: str) -> bool:
|
2017-11-15 12:07:42 +03:00
|
|
|
"""
|
|
|
|
Returns True if the dirstate contains a tracked (not removed) file
|
|
|
|
in this directory.
|
|
|
|
"""
|
|
|
|
return d in self._dirs
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def hasdir(self, d: str) -> bool:
|
2017-09-26 13:56:20 +03:00
|
|
|
"""
|
2017-11-15 12:07:42 +03:00
|
|
|
Returns True if the dirstate contains a file (tracked or removed)
|
|
|
|
in this directory.
|
|
|
|
"""
|
|
|
|
return d in self._alldirs
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-05-10 03:03:38 +03:00
|
|
|
# pyre-fixme[3]: Return type must be annotated.
|
|
|
|
def _dirs(self):
|
2020-08-13 18:24:26 +03:00
|
|
|
"""
|
|
|
|
Build a set of directories present in the dirstate.
|
|
|
|
|
|
|
|
Some dirstate implementation (eden for instance), don't support this,
|
|
|
|
and it's thus a good idea to test if "_dirs" is in self.__dict__.
|
|
|
|
"""
|
2020-01-31 04:31:54 +03:00
|
|
|
return util.dirs((p for (p, s) in pycompat.iteritems(self._map) if s[0] != "r"))
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-05-10 03:03:38 +03:00
|
|
|
# pyre-fixme[3]: Return type must be annotated.
|
|
|
|
def _alldirs(self):
|
2017-11-15 12:07:42 +03:00
|
|
|
return util.dirs(self._map)
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def _opendirstatefile(self) -> "BinaryIO":
|
2017-09-26 13:56:20 +03:00
|
|
|
fp, mode = txnutil.trypending(self._root, self._opener, self._filename)
|
|
|
|
if self._pendingmode is not None and self._pendingmode != mode:
|
|
|
|
fp.close()
|
2020-03-12 04:31:12 +03:00
|
|
|
raise error.Abort(_("working directory state may be changed parallelly"))
|
2017-09-26 13:56:20 +03:00
|
|
|
self._pendingmode = mode
|
|
|
|
return fp
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def parents(self) -> "Tuple[bytes, bytes]":
|
2020-08-12 07:43:21 +03:00
|
|
|
parents = self._parents
|
|
|
|
if not parents:
|
2017-09-26 13:56:20 +03:00
|
|
|
try:
|
|
|
|
fp = self._opendirstatefile()
|
|
|
|
st = fp.read(40)
|
|
|
|
fp.close()
|
|
|
|
except IOError as err:
|
|
|
|
if err.errno != errno.ENOENT:
|
|
|
|
raise
|
|
|
|
# File doesn't exist, so the current state is empty
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
st = ""
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2017-09-26 13:56:20 +03:00
|
|
|
l = len(st)
|
|
|
|
if l == 40:
|
2020-08-12 07:43:21 +03:00
|
|
|
parents = st[:20], st[20:40]
|
2017-09-26 13:56:20 +03:00
|
|
|
elif l == 0:
|
2020-08-12 07:43:21 +03:00
|
|
|
parents = (nullid, nullid)
|
2017-09-26 13:56:20 +03:00
|
|
|
else:
|
2020-03-12 04:31:12 +03:00
|
|
|
raise error.Abort(_("working directory state appears damaged!"))
|
2020-08-12 07:43:21 +03:00
|
|
|
self._parents = parents
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
return parents
|
2017-09-26 13:56:20 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def setparents(self, p1: bytes, p2: bytes) -> None:
|
2017-09-26 13:56:20 +03:00
|
|
|
self._parents = (p1, p2)
|
|
|
|
self._dirtyparents = True
|
2017-10-05 21:34:41 +03:00
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def read(self) -> None:
|
2017-10-05 21:34:41 +03:00
|
|
|
# ignore HG_PENDING because identity is used only for writing
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
self.identity = util.filestat.frompath(self._opener.join(self._filename))
|
2017-10-05 21:34:41 +03:00
|
|
|
|
2017-10-05 21:34:41 +03:00
|
|
|
try:
|
|
|
|
fp = self._opendirstatefile()
|
|
|
|
try:
|
|
|
|
st = fp.read()
|
|
|
|
finally:
|
|
|
|
fp.close()
|
|
|
|
except IOError as err:
|
|
|
|
if err.errno != errno.ENOENT:
|
|
|
|
raise
|
|
|
|
return
|
|
|
|
if not st:
|
|
|
|
return
|
|
|
|
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
if util.safehasattr(parsers, "dict_new_presized"):
|
2017-10-05 21:34:41 +03:00
|
|
|
# Make an estimate of the number of files in the dirstate based on
|
|
|
|
# its size. From a linear regression on a set of real-world repos,
|
|
|
|
# all over 10,000 files, the size of a dirstate entry is 85
|
|
|
|
# bytes. The cost of resizing is significantly higher than the cost
|
|
|
|
# of filling in a larger presized dict, so subtract 20% from the
|
|
|
|
# size.
|
|
|
|
#
|
|
|
|
# This heuristic is imperfect in many ways, so in a future dirstate
|
|
|
|
# format update it makes sense to just record the number of entries
|
|
|
|
# on write.
|
2020-02-26 23:45:42 +03:00
|
|
|
self._map = parsers.dict_new_presized(len(st) // 71)
|
2017-10-05 21:34:41 +03:00
|
|
|
|
|
|
|
# Python's garbage collector triggers a GC each time a certain number
|
|
|
|
# of container objects (the number being defined by
|
|
|
|
# gc.get_threshold()) are allocated. parse_dirstate creates a tuple
|
|
|
|
# for each file in the dirstate. The C version then immediately marks
|
|
|
|
# them as not to be tracked by the collector. However, this has no
|
|
|
|
# effect on when GCs are triggered, only on what objects the GC looks
|
|
|
|
# into. This means that O(number of files) GCs are unavoidable.
|
|
|
|
# Depending on when in the process's lifetime the dirstate is parsed,
|
|
|
|
# this can get very expensive. As a workaround, disable GC while
|
|
|
|
# parsing the dirstate.
|
|
|
|
#
|
|
|
|
# (we cannot decorate the function directly since it is in a C module)
|
|
|
|
parse_dirstate = util.nogc(parsers.parse_dirstate)
|
|
|
|
p = parse_dirstate(self._map, self.copymap, st)
|
|
|
|
if not self._dirtyparents:
|
|
|
|
self.setparents(*p)
|
2017-10-05 21:34:41 +03:00
|
|
|
|
2017-10-28 22:35:54 +03:00
|
|
|
# Avoid excess attribute lookups by fast pathing certain checks
|
2022-02-10 01:26:09 +03:00
|
|
|
self.__contains__: "Callable[[str], bool]" = self._map.__contains__
|
|
|
|
self.__getitem__: "Callable[[str], dirstatetuple]" = self._map.__getitem__
|
2017-10-28 22:35:54 +03:00
|
|
|
self.get = self._map.get
|
|
|
|
|
2022-02-10 01:26:09 +03:00
|
|
|
def write(self, st: "BinaryIO", now: int) -> None:
|
codemod: join the auto-formatter party
Summary:
Turned on the auto formatter. Ran `arc lint --apply-patches --take BLACK **/*.py`.
Then run `arc lint` again so some other autofixers like spellchecker etc. looked
at the code base. Manually accept the changes whenever they make sense, or use
a workaround (ex. changing "dict()" to "dict constructor") where autofix is false
positive. Disabled linters on files that are hard (i18n/polib.py) to fix, or less
interesting to fix (hgsubversion tests), or cannot be fixed without breaking
OSS build (FBPYTHON4).
Conflicted linters (test-check-module-imports.t, part of test-check-code.t,
test-check-pyflakes.t) are removed or disabled.
Duplicated linters (test-check-pyflakes.t, test-check-pylint.t) are removed.
An issue of the auto-formatter is lines are no longer guarnateed to be <= 80
chars. But that seems less important comparing with the benefit auto-formatter
provides.
As we're here, also remove test-check-py3-compat.t, as it is currently broken
if `PYTHON3=/bin/python3` is set.
Reviewed By: wez, phillco, simpkins, pkaush, singhsrb
Differential Revision: D8173629
fbshipit-source-id: 90e248ae0c5e6eaadbe25520a6ee42d32005621b
2018-05-26 07:34:37 +03:00
|
|
|
st.write(parsers.pack_dirstate(self._map, self.copymap, self.parents(), now))
|
2017-10-05 21:34:41 +03:00
|
|
|
st.close()
|
|
|
|
self._dirtyparents = False
|
2017-10-05 21:34:41 +03:00
|
|
|
self.nonnormalset, self.otherparentset = self.nonnormalentries()
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def nonnormalset(self) -> "Set[str]":
|
2017-10-05 21:34:41 +03:00
|
|
|
nonnorm, otherparents = self.nonnormalentries()
|
|
|
|
self.otherparentset = otherparents
|
|
|
|
return nonnorm
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def otherparentset(self) -> "Set[str]":
|
2017-10-05 21:34:41 +03:00
|
|
|
nonnorm, otherparents = self.nonnormalentries()
|
|
|
|
self.nonnormalset = nonnorm
|
|
|
|
return otherparents
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def identity(self) -> "util.filestat":
|
2017-10-27 02:15:36 +03:00
|
|
|
self._map
|
2017-10-05 21:34:41 +03:00
|
|
|
return self.identity
|
|
|
|
|
2020-08-12 07:43:21 +03:00
|
|
|
@util.propertycache
|
2022-02-10 01:26:09 +03:00
|
|
|
def dirfoldmap(self) -> "Dict[str, str]":
|
2017-10-05 21:34:41 +03:00
|
|
|
f = {}
|
|
|
|
normcase = util.normcase
|
2020-08-13 18:24:26 +03:00
|
|
|
if "_dirs" in self.__dict__:
|
|
|
|
for name in self._dirs:
|
|
|
|
f[normcase(name)] = name
|
2017-10-05 21:34:41 +03:00
|
|
|
return f
|