HEX

File: //usr/lib/python3/dist-packages/mercurial/interfaces/__pycache__/repository.cpython-310.pyc

�]Lb��@s�ddlmZddlmZddlmZddlmZdZdZ d Z
d
ZdZdZ
d
ZdZdZdZeeBeBeBZdZdZdZdZdZdZdZdZdZdZdZdZdZehZ eeeeeeeehZ!e!�"�Z#e#�$e�Gdd�dej%�Z&Gd d!�d!ej%�Z'Gd"d#�d#ej%�Z(Gd$d%�d%ej%�Z)Gd&d'�d'ej%�Z*Gd(d)�d)ej%�Z+Gd*d+�d+e&e'e+�Z,Gd,d-�d-e&e'e+�Z-e�.e,�Gd.d/�d/e/��Z0Gd0d1�d1ej%�Z1Gd2d3�d3ej%�Z2Gd4d5�d5ej%�Z3Gd6d7�d7ej%�Z4Gd8d9�d9ej%�Z5Gd:d;�d;ej%�Z6Gd<d=�d=e4e5e6�Z7Gd>d?�d?ej%�Z8Gd@dA�dAej%�Z9GdBdC�dCej%�Z:GdDdE�dEe:�Z;GdFdG�dGe:�Z<GdHdI�dIej%�Z=GdJdK�dKej%�Z>GdLdM�dMej%�Z?GdNdO�dOej%�Z@GdPdQ�dQe@e?�ZAGdRdS�dSej%�ZBdTS)U�)�absolute_import�)�_)�error�)�utilsrevlogfilestoragessharedstoreslfssstreamclones side-datasshallowfilestoragei�i@i isdefaultsprevioussfulltextsp1s
branchmap-allsbranchmap-servedschangelog-caches
full-manifestsfile-node-tagssmanifestlog-cachesrev-branch-cachestags-defaultstags-servedc@sBeZdZdZe�d�Zdd�Zdd�Zdd�Z d d
�Z
dd�Zd
S)�ipeerconnectiona*Represents a "connection" to a repository.

This is the base interface for representing a connection to a repository.
It holds basic properties and methods applicable to all peer types.

This is not a complete interface definition and should not be used
outside of this module.
zui.ui instancecC�dS)a�Returns a URL string representing this peer.

Currently, implementations expose the raw URL used to construct the
instance. It may contain credentials as part of the URL. The
expectations of the value aren't well-defined and this could lead to
data leakage.

TODO audit/clean consumers and more clearly define the contents of this
value.
N�r
r
r
�A/usr/lib/python3/dist-packages/mercurial/interfaces/repository.py�urll�zipeerconnection.urlcCr )z�Returns a local repository instance.

If the peer represents a local repository, returns an object that
can be used to interface with it. Otherwise returns ``None``.
Nr
r
r
r
r�localxr
zipeerconnection.localcCr )zlReturns an object conforming to this interface.

Most implementations will ``return self``.
Nr
r
r
r
r�peerr
zipeerconnection.peercCr )z;Returns a boolean indicating if this peer can be pushed to.Nr
r
r
r
r�canpush�r
zipeerconnection.canpushcCr )z�Close the connection to this peer.

This is called when the peer will no longer be used. Resources
associated with the peer should be cleaned up.
Nr
r
r
r
r�close�r
zipeerconnection.closeN)�__name__�
__module__�__qualname__�__doc__�
interfaceutil� Attribute�uirrrrrr
r
r
rr`s
rc@� eZdZdZdd�Zdd�ZdS)�ipeercapabilitiesz+Peer sub-interface related to capabilities.cCr )a5Determine support for a named capability.

Returns ``False`` if capability not supported.

Returns ``True`` if boolean capability is supported. Returns a string
if capability support is non-boolean.

Capability strings may or may not map to wire protocol capabilities.
Nr
)�namer
r
r�capable�r
zipeercapabilities.capablecCr )zsRequire a capability to be present.

Raises a ``CapabilityError`` if the capability isn't present.
Nr
)r�purposer
r
r�
requirecap�r
zipeercapabilities.requirecapN)rrrrrrr
r
r
rr�src@sreZdZdZdd�Zdd�Zdd�Zdd d
�Zdd�Zd
d�Z dd�Z
dd�Zdd�Zdd�Z
dd�Zdd�ZdS)�
ipeercommandsz�Client-side interface for communicating over the wire protocol.

This interface is used as a gateway to the Mercurial wire protocol.
methods commonly call wire protocol commands of the same name.
cCr )z�Obtain heads in named branches.

Returns a dict mapping branch name to an iterable of nodes that are
heads on that branch.
Nr
r
r
r
r� branchmap�r
zipeercommands.branchmapcCr )zXObtain capabilities of the peer.

Returns a set of string capabilities.
Nr
r
r
r
r�capabilities�r
zipeercommands.capabilitiescCr )zjObtains the clone bundles manifest for the repo.

Returns the manifest as unparsed bytes.
Nr
r
r
r
r�clonebundles�r
zipeercommands.clonebundlesNcCr )z?Used to facilitate debugging of arguments passed over the wire.Nr
��one�two�three�four�fiver
r
r�
debugwireargs�r
zipeercommands.debugwireargscKr )z�Obtain remote repository data as a bundle.

This command is how the bulk of repository data is transferred from
the peer to the local repository

Returns a generator of bundle data.
Nr
)�source�kwargsr
r
r� getbundle�r
zipeercommands.getbundlecCr )zfDetermine all known head revisions in the peer.

Returns an iterable of binary nodes.
Nr
r
r
r
r�heads�r
zipeercommands.headscCr )z�Determine whether multiple nodes are known.

Accepts an iterable of nodes whose presence to check for.

Returns an iterable of booleans indicating of the corresponding node
at that index is known to the peer.
Nr
��nodesr
r
r�known�r
zipeercommands.knowncCr )z[Obtain all keys in a pushkey namespace.

Returns an iterable of key names.
Nr
�� namespacer
r
r�listkeys�r
zipeercommands.listkeyscCr )zqResolve a value to a known revision.

Returns a binary node of the resolved revision on success.
Nr
��keyr
r
r�lookup�r
zipeercommands.lookupcCr )aSet a value using the ``pushkey`` protocol.

Arguments correspond to the pushkey namespace and key to operate on and
the old and new values for that key.

Returns a string with the peer result. The value inside varies by the
namespace.
Nr
�r2r5�old�newr
r
r�pushkey�r
zipeercommands.pushkeycCr )zfObtain streaming clone data.

Successful result should be a generator of data chunks.
Nr
r
r
r
r�
stream_out�r
zipeercommands.stream_outcCr )z�Transfer repository data to the peer.

This is how the bulk of data during a push is transferred.

Returns the integer number of heads added to the peer.
Nr
)�bundler-rr
r
r�unbundle�r
zipeercommands.unbundle�NNN)rrrrr r!r"r)r,r-r0r3r6r:r;r=r
r
r
rr�s

rc@�0eZdZdZdd�Zdd�Zdd�Zdd �Zd
S)�ipeerlegacycommandsa Interface for implementing support for legacy wire protocol commands.

Wire protocol commands transition to legacy status when they are no longer
used by modern clients. To facilitate identifying which commands are
legacy, the interfaces are split.
cCr )z�Obtain nodes between pairs of nodes.

``pairs`` is an iterable of node pairs.

Returns an iterable of iterables of nodes corresponding to each
requested pair.
Nr
��pairsr
r
r�betweenr
zipeerlegacycommands.betweencCr )aObtain ancestor changesets of specific nodes back to a branch point.

For each requested node, the peer finds the first ancestor node that is
a DAG root or is a merge.

Returns an iterable of iterables with the resolved values for each node.
Nr
r.r
r
r�branchesr
zipeerlegacycommands.branchescCr )zBObtain a changegroup with data for descendants of specified nodes.Nr
)r/r*r
r
r�changegroupr
zipeerlegacycommands.changegroupcC�dS�Nr
)�basesr-r*r
r
r�changegroupsubset�z%ipeerlegacycommands.changegroupsubsetN)rrrrrCrDrErIr
r
r
rr@�s r@c@s(eZdZdZdd�Zdd�Zdd�ZdS) �ipeercommandexecutoraDRepresents a mechanism to execute remote commands.

This is the primary interface for requesting that wire protocol commands
be executed. Instances of this interface are active in a context manager
and have a well-defined lifetime. When the context manager exits, all
outstanding requests are waited on.
cCr )a�Request that a named command be executed.

Receives the command name and a dictionary of command arguments.

Returns a ``concurrent.futures.Future`` that will resolve to the
result of that command request. That exact value is left up to
the implementation and possibly varies by command.

Not all commands can coexist with other commands in an executor
instance: it depends on the underlying wire protocol transport being
used and the command itself.

Implementations MAY call ``sendcommands()`` automatically if the
requested command can not coexist with other commands in this executor.

Implementations MAY call ``sendcommands()`` automatically when the
future's ``result()`` is called. So, consumers using multiple
commands with an executor MUST ensure that ``result()`` is not called
until all command requests have been issued.
Nr
)r�argsr
r
r�callcommand)r
z ipeercommandexecutor.callcommandcCr )abTrigger submission of queued command requests.

Not all transports submit commands as soon as they are requested to
run. When called, this method forces queued command requests to be
issued. It will no-op if all commands have already been sent.

When called, no more new commands may be issued with this executor.
Nr
r
r
r
r�sendcommands?r
z!ipeercommandexecutor.sendcommandscCr )aySignal that this command request is finished.

When called, no more new commands may be issued. All outstanding
commands that have previously been issued are waited on before
returning. This not only includes waiting for the futures to resolve,
but also waiting for all response data to arrive. In other words,
calling this waits for all on-wire state for issued command requests
to finish.

When used as a context manager, this method is called when exiting the
context manager.

This method may call ``sendcommands()`` if there are buffered commands.
Nr
r
r
r
rrIr
zipeercommandexecutor.closeN)rrrrrMrNrr
r
r
rrK s

rKc@s"eZdZdZe�d�Zdd�ZdS)�
ipeerrequestsz+Interface for executing commands on a peer.zBTrue if the peer cannot receive large argument value for commands.cCr )aA context manager that resolves to an ipeercommandexecutor.

The object this resolves to can be used to issue command requests
to the peer.

Callers should call its ``callcommand`` method to issue command
requests.

A new executor should be obtained for each distinct set of commands
(possibly just a single command) that the consumer wants to execute
as part of a single operation or round trip. This is because some
peers are half-duplex and/or don't support persistent connections.
e.g. in the case of HTTP peers, commands sent to an executor represent
a single HTTP request. While some peers may support multiple command
sends over the wire per executor, consumers need to code to the least
capable peer. So it should be assumed that command executors buffer
called commands until they are told to send them and that each
command executor could result in a new connection or wire-level request
being issued.
Nr
r
r
r
r�commandexecutorar
zipeerrequests.commandexecutorN)rrrrrr�limitedargumentsrPr
r
r
rrOZs�rOc@�eZdZdZdS)� ipeerbasezeUnified interface for peer repositories.

All peer instances must conform to this interface.
N�rrrrr
r
r
rrSxsrSc@seZdZdZe�d�ZdS)�ipeerv2z9Unified peer interface for wire protocol version 2 peers.z1Data structure holding description of server API.N)rrrrrr�
apidescriptorr
r
r
rrUs
�rUc@s$eZdZdZdZdd�Zdd�ZdS)rz!Base class for peer repositories.FcCsH|��}||vr
dSd|}|D]}|�|�r!|t|�d�SqdS)NTs%s=F)r!�
startswith�len)�selfr�caps�capr
r
rr�s
�zpeer.capablecCs$|�|�rdSt�td�||f��)NsAcannot %s; remote repository does not support the '%s' capability)rr�CapabilityErrorr)rYrrr
r
rr�s
���zpeer.requirecapN)rrrrrQrrr
r
r
rr�s
rc@s.eZdZdZe�d�Ze�d�Ze�d�ZdS)�iverifyproblemaRepresents a problem with the integrity of the repository.

Instances of this interface are emitted to describe an integrity issue
with a repository (e.g. corrupt storage, missing data, etc).

Instances are essentially messages associated with severity.
z'Message indicating a non-fatal problem.z#Message indicating a fatal problem.zsRevision encountering the problem.

``None`` means the problem doesn't apply to a single revision.
N) rrrrrr�warningr�noder
r
r
rr]�s�
�r]c@s~eZdZdZe�d�Ze�d�Ze�d�Ze�d�Z e�d�Z
e�d�Ze�d�Ze�d �Z
e�d
�Ze�d�Ze�d�Zd
S)�irevisiondeltaa�Represents a delta between one revision and another.

Instances convey enough information to allow a revision to be exchanged
with another repository.

Instances represent the fulltext revision data or a delta against
another revision. Therefore the ``revision`` and ``delta`` attributes
are mutually exclusive.

Typically used for changegroup generation.
z20 byte node of this revision.z,20 byte node of 1st parent of this revision.z,20 byte node of 2nd parent of this revision.z>20 byte node of the changelog revision this node is linked to.z�2 bytes of integer flags that apply to this revision.

This is a bitwise composition of the ``REVISION_FLAG_*`` constants.
z�20 byte node of the revision this data is a delta against.

``nullid`` indicates that the revision is a full revision and not
a delta.
zmSize of base revision this delta is against.

May be ``None`` if ``basenode`` is ``nullid``.
z,Raw fulltext of revision data for this node.z\Delta between ``basenode`` and ``node``.

Stored in the bdiff delta format.
z*Raw sidedata bytes for the given revision.z�Single byte of integer flags that can influence the protocol.

This is a bitwise composition of the ``storageutil.CG_FLAG*`` constants.
N)rrrrrrr_�p1node�p2node�linknode�flags�basenode�baserevisionsize�revision�delta�sidedata�protocol_flagsr
r
r
rr`�sB
����������r`c@r?)�ifilerevisionssequencea,Contains index data for all revisions of a file.

Types implementing this behave like lists of tuples. The index
in the list corresponds to the revision number. The values contain
index metadata.

The *null* revision (revision number -1) is always the last item
in the index.
cCr )zThe total number of revisions.Nr
r
r
r
r�__len__r
zifilerevisionssequence.__len__cCr )a�Returns the object having a specific revision number.

Returns an 8-tuple with the following fields:

offset+flags
Contains the offset and flags for the revision. 64-bit unsigned
integer where first 6 bytes are the offset and the next 2 bytes
are flags. The offset can be 0 if it is not used by the store.
compressed size
Size of the revision data in the store. It can be 0 if it isn't
needed by the store.
uncompressed size
Fulltext size. It can be 0 if it isn't needed by the store.
base revision
Revision number of revision the delta for storage is encoded
against. -1 indicates not encoded against a base revision.
link revision
Revision number of changelog revision this entry is related to.
p1 revision
Revision number of 1st parent. -1 if no 1st parent.
p2 revision
Revision number of 2nd parent. -1 if no 1st parent.
node
Binary node value for this revision number.

Negative values should index off the end of the sequence. ``-1``
should return the null revision. ``-2`` should return the most
recent revision.
Nr
��revr
r
r�__getitem__r
z"ifilerevisionssequence.__getitem__cCr )z!Whether a revision number exists.Nr
rmr
r
r�__contains__2r
z#ifilerevisionssequence.__contains__cCr )z.Add an item to the index at specific revision.Nr
)rY�i�entryr
r
r�insert5r
zifilerevisionssequence.insertN)rrrrrlrorprsr
r
r
rrks
rkc@s�eZdZdZe�d�Zdd�Zdd�Zdd�Z d#dd�Z
d
d�Zdd�Zdd�Z
dd�Zdd�Zdd�Zdd�Zdd�Zdd�Zd$dd �Zd!d"�Zd
S)%�
ifileindexa�Storage interface for index data of a single file.

File storage data is divided into index metadata and data storage.
This interface defines the index portion of the interface.

The index logically consists of:

* A mapping between revision numbers and nodes.
* DAG data (storing and querying the relationship between nodes).
* Metadata to facilitate storage.
z1node for the null revision for use as delta base.cCr )z4Obtain the number of revisions stored for this file.Nr
r
r
r
rrlJr
zifileindex.__len__cCr )z,Iterate over revision numbers for this file.Nr
r
r
r
r�__iter__Mr
zifileindex.__iter__cCr )aReturns a bool indicating if a node is known to this store.

Implementations must only return True for full, binary node values:
hex nodes, revision numbers, and partial node matches must be
rejected.

The null node is never present.
Nr
�r_r
r
r�hasnodePr
zifileindex.hasnoderNcCr )z:Iterate over revision numbers for this file, with control.Nr
��start�stopr
r
r�revsZr
zifileindex.revscCr )zuReturns a 2-tuple of parent nodes for a revision.

Values will be ``nullid`` if the parent is empty.
Nr
rvr
r
r�parents]r
zifileindex.parentscCr �z0Like parents() but operates on revision numbers.Nr
rmr
r
r�
parentrevscr
zifileindex.parentrevscCr )zqObtain the revision number given a node.

Raises ``error.LookupError`` if the node is not known.
Nr
rvr
r
rrnfr
zifileindex.revcCr )zpObtain the node value given a revision number.

Raises ``IndexError`` if the node is not known.
Nr
rmr
r
rr_lr
zifileindex.nodecCr )z�Attempt to resolve a value to a node.

Value can be a binary node, hex node, revision number, or a string
that can be converted to an integer.

Raises ``error.LookupError`` if a node could not be resolved.
Nr
rvr
r
rr6rr
zifileindex.lookupcCr �z=Obtain the changeset revision number a revision is linked to.Nr
rmr
r
r�linkrev{r
zifileindex.linkrevcCr )z6Return whether a revision's content has been censored.Nr
rmr
r
r�
iscensored~r
zifileindex.iscensoredcCr )z|Obtain an iterable of nodes containing heads of common ancestors.

See ``ancestor.commonancestorsheads()``.
Nr
)�node1�node2r
r
r�commonancestorsheads�r
zifileindex.commonancestorsheadscCr )z�Obtain descendant revision numbers for a set of revision numbers.

If ``nullrev`` is in the set, this is equivalent to ``revs()``.
Nr
)r{r
r
r�descendants�r
zifileindex.descendantscCr )agObtain a list of nodes that are DAG heads, with control.

The set of revisions examined can be limited by specifying
``start`` and ``stop``. ``start`` is a node. ``stop`` is an
iterable of nodes. DAG traversal starts at earlier revision
``start`` and iterates forward until any node in ``stop`` is
encountered.
Nr
rxr
r
rr-�r
zifileindex.headscCr )zTObtain nodes that are children of a node.

Returns a list of nodes.
Nr
rvr
r
r�children�r
zifileindex.children)rN�NN)rrrrrr�nullidrlrurwr{r|r~rnr_r6r�r�r�r�r-r�r
r
r
rrt9s(�

rtc@sTeZdZdZdd�Zddd�Zdd�Zd d
�Zdd�Zd
d�Z ddde
fdd�ZdS)� ifiledataz�Storage interface for data storage of a specific file.

This complements ``ifileindex`` and provides an interface for accessing
data for a tracked file.
cCr )ziObtain the fulltext size of file data.

Any metadata is excluded from size measurements.
Nr
rmr
r
r�size�r
zifiledata.sizeFcCr )ajObtain fulltext data for a node.

By default, any storage transformations are applied before the data
is returned. If ``raw`` is True, non-raw storage transformations
are not applied.

The fulltext data may contain a header containing metadata. Most
consumers should use ``read()`` to obtain the actual file data.
Nr
)r_�rawr
r
rrg�r
zifiledata.revisioncCr �zObtain raw data for a node.Nr
rvr
r
r�rawdata�r
zifiledata.rawdatacCr )z�Resolve file fulltext data.

This is similar to ``revision()`` except any metadata in the data
headers is stripped.
Nr
rvr
r
r�read�r
zifiledata.readcCr )z�Obtain copy metadata for a node.

Returns ``False`` if no copy metadata is stored or a 2-tuple of
(path, node) from which this revision was copied.
Nr
rvr
r
r�renamed�r
zifiledata.renamedcCr )z�Compare fulltext to another revision.

Returns True if the fulltext is different from what is stored.

This takes copy metadata into account.

TODO better document the copy metadata and censoring logic.
Nr
�r_�fulltextr
r
r�cmp�r
z
ifiledata.cmpNcCr )a- Produce ``irevisiondelta`` for revisions.

Given an iterable of nodes, emits objects conforming to the
``irevisiondelta`` interface that describe revisions in storage.

This method is a generator.

The input nodes may be unordered. Implementations must ensure that a
node's parents are emitted before the node itself. Transitively, this
means that a node may only be emitted once all its ancestors in
``nodes`` have also been emitted.

By default, emits "index" data (the ``node``, ``p1node``, and
``p2node`` attributes). If ``revisiondata`` is set, revision data
will also be present on the emitted objects.

With default argument values, implementations can choose to emit
either fulltext revision data or a delta. When emitting deltas,
implementations must consider whether the delta's base revision
fulltext is available to the receiver.

The base revision fulltext is guaranteed to be available if any of
the following are met:

* Its fulltext revision was emitted by this method call.
* A delta for that revision was emitted by this method call.
* ``assumehaveparentrevisions`` is True and the base revision is a
parent of the node.

``nodesorder`` can be used to control the order that revisions are
emitted. By default, revisions can be reordered as long as they are
in DAG topological order (see above). If the value is ``nodes``,
the iteration order from ``nodes`` should be used. If the value is
``storage``, then the native order from the backing storage layer
is used. (Not all storage layers will have strong ordering and behavior
of this mode is storage-dependent.) ``nodes`` ordering can force
revisions to be emitted before their ancestors, so consumers should
use it with care.

The ``linknode`` attribute on the returned ``irevisiondelta`` may not
be set and it is the caller's responsibility to resolve it, if needed.

If ``deltamode`` is CG_DELTAMODE_PREV and revision data is requested,
all revision data should be emitted as deltas against the revision
emitted just prior. The initial revision should be a delta against its
1st parent.
Nr
)r/�
nodesorder�revisiondata�assumehaveparentrevisions� deltamoder
r
r�
emitrevisions�r
zifiledata.emitrevisions�F)rrrrr�rgr�r�r�r��CG_DELTAMODE_STDr�r
r
r
rr��s
�r�c@sReZdZdZdd�Z ddd�Z dd d
�Zddd
�Zdd�Zdd�Z dS)�
ifilemutationz8Storage interface for mutation events of a tracked file.cCr )aAdd a new revision to the store.

Takes file data, dictionary of metadata, a transaction, linkrev,
and parent nodes.

Returns the node that was added.

May no-op if a revision matching the supplied data is already stored.
Nr
)�filedata�meta�transactionr��p1�p2r
r
r�addr
zifilemutation.addNrcCr )a�Add a new revision to the store and return its number.

This is similar to ``add()`` except it operates at a lower level.

The data passed in already contains a metadata header, if any.

``node`` and ``flags`` can be used to define the expected node and
the flags to use with storage. ``flags`` is a bitwise value composed
of the various ``REVISION_FLAG_*`` constants.

``add()`` is usually called when adding files from e.g. the working
directory. ``addrevision()`` is often called by ``add()`` and for
scenarios where revision data has already been computed, such as when
applying raw data from a peer repo.
Nr
)r�r�r�r�r�r_rd�
cachedeltar
r
r�addrevisionr
zifilemutation.addrevisionFcCr )a�Process a series of deltas for storage.

``deltas`` is an iterable of 7-tuples of
(node, p1, p2, linknode, deltabase, delta, flags) defining revisions
to add.

The ``delta`` field contains ``mpatch`` data to apply to a base
revision, identified by ``deltabase``. The base node can be
``nullid``, in which case the header from the delta can be ignored
and the delta used as the fulltext.

``alwayscache`` instructs the lower layers to cache the content of the
newly added revision, even if it needs to be explicitly computed.
This used to be the default when ``addrevisioncb`` was provided up to
Mercurial 5.8.

``addrevisioncb`` should be called for each new rev as it is committed.
``duplicaterevisioncb`` should be called for all revs with a
pre-existing node.

``maybemissingparents`` is a bool indicating whether the incoming
data may reference parents/ancestor revisions that aren't present.
This flag is set when receiving data into a "shallow" store that
doesn't hold all history.

Returns a list of nodes that were processed. A node will be in the list
even if it existed in the store previously.
Nr
)�deltas�
linkmapperr��
addrevisioncb�duplicaterevisioncb�maybemissingparentsr
r
r�addgroup1r
zifilemutation.addgroup�cCr )a�Remove the content of a single revision.

The specified ``node`` will have its content purged from storage.
Future attempts to access the revision data for this node will
result in failure.

A ``tombstone`` message can optionally be stored. This message may be
displayed to users when they attempt to access the missing revision
data.

Storage backends may have stored deltas against the previous content
in this revision. As part of censoring a revision, these storage
backends are expected to rewrite any internally stored deltas such
that they no longer reference the deleted content.
Nr
)�trr_� tombstoner
r
r�censorrevisionVr
zifilemutation.censorrevisioncCr )aoFind the minimum revision that must be stripped to strip a linkrev.

Returns a 2-tuple containing the minimum revision number and a set
of all revisions numbers that would be broken by this strip.

TODO this is highly revlog centric and should be abstracted into
a higher-level deletion API. ``repair.strip()`` relies on this.
Nr
��minlinkr
r
r�
getstrippointgr
zifilemutation.getstrippointcCr )a@Remove storage of items starting at a linkrev.

This uses ``getstrippoint()`` to determine the first node to remove.
Then it effectively truncates storage for all revisions after that.

TODO this is highly revlog centric and should be abstracted into a
higher-level deletion API.
Nr
�r�r�r
r
r�stripqr
zifilemutation.strip)NrN�NNF)r�)
rrrrr�r�r�r�r�r�r
r
r
rr� s
�
�
%
r�c@s4eZdZdZdd�Z d
dd�Zdd�Zd S)�ifilestoragez5Complete storage interface for a single tracked file.cCr )z�Obtain paths that are backing storage for this file.

TODO this is used heavily by verify code and there should probably
be a better API for that.
Nr
r
r
r
r�filesr
zifilestorage.filesFcCr )aObtain information about storage for this file's data.

Returns a dict describing storage for this tracked path. The keys
in the dict map to arguments of the same. The arguments are bools
indicating whether to calculate and obtain that data.

exclusivefiles
Iterable of (vfs, path) describing files that are exclusively
used to back storage for this tracked path.

sharedfiles
Iterable of (vfs, path) describing files that are used to back
storage for this tracked path. Those files may also provide storage
for other stored entities.

revisionscount
Number of revisions available for retrieval.

trackedsize
Total size in bytes of all tracked revisions. This is a sum of the
length of the fulltext of all revisions.

storedsize
Total size in bytes used to store data for all tracked revisions.
This is commonly less than ``trackedsize`` due to internal usage
of deltas rather than fulltext revisions.

Not all storage backends may support all queries are have a reasonable
value to use. In that case, the value should be set to ``None`` and
callers are expected to handle this special value.
Nr
��exclusivefiles�sharedfiles�revisionscount�trackedsize�
storedsizer
r
r�storageinfo�r
zifilestorage.storageinfocCr )a�Verifies the integrity of file storage.

``state`` is a dict holding state of the verifier process. It can be
used to communicate data between invocations of multiple storage
primitives.

If individual revisions cannot have their revision content resolved,
the method is expected to set the ``skipread`` key to a set of nodes
that encountered problems. If set, the method can also add the node(s)
to ``safe_renamed`` in order to indicate nodes that may perform the
rename checks with currently accessible data.

The method yields objects conforming to the ``iverifyproblem``
interface.
Nr
��stater
r
r�verifyintegrity�r
zifilestorage.verifyintegrityN�FFFFF)rrrrr�r�r�r
r
r
rr�|s
�'r�c@r?)�idirsz�Interface representing a collection of directories from paths.

This interface is essentially a derived data structure representing
directories from a collection of paths.
cCr )zlAdd a path to the collection.

All directories in the path will be added to the collection.
Nr
��pathr
r
r�addpath�r
z
idirs.addpathcCr )z�Remove a path from the collection.

If the removal was the last path in a particular directory, the
directory is removed from the collection.
Nr
r�r
r
r�delpath�r
z
idirs.delpathcCr )z9Iterate over the directories in this collection of paths.Nr
r
r
r
rru�r
zidirs.__iter__cCr )z3Whether a specific directory is in this collection.Nr
r�r
r
rrp�r
zidirs.__contains__N)rrrrr�r�rurpr
r
r
rr��sr�c@s�eZdZdZdd�Zdd�Zdd�Zdd �ZeZd
d�Z dd
�Z
dd�Zdd�Zdd�Z
dd�Zd4dd�Zdd�Zdd�Zdd�Zd5d d!�Zd"d#�Zd4d$d%�Zd&d'�Zd(d)�Zd*d+�Zd,d-�Zd.d/�Zd0d1�Zd2d3�ZdS)6�
imanifestdictz�Interface representing a manifest data structure.

A manifest is effectively a dict mapping paths to entries. Each entry
consists of a binary node and extra flags affecting that entry.
cCr )z�Returns the binary node value for a path in the manifest.

Raises ``KeyError`` if the path does not exist in the manifest.

Equivalent to ``self.find(path)[0]``.
Nr
r�r
r
rro�r
zimanifestdict.__getitem__cCr )z�Returns the entry for a path in the manifest.

Returns a 2-tuple of (node, flags).

Raises ``KeyError`` if the path does not exist in the manifest.
Nr
r�r
r
r�find�r
zimanifestdict.findcCr )z-Return the number of entries in the manifest.Nr
r
r
r
rrl�r
zimanifestdict.__len__cCr )z:Returns True if the manifest has entries, False otherwise.Nr
r
r
r
r�__nonzero__�r
zimanifestdict.__nonzero__cCr )z�Define the node value for a path in the manifest.

If the path is already in the manifest, its flags will be copied to
the new entry.
Nr
)r�r_r
r
r�__setitem__�r
zimanifestdict.__setitem__cCr )z&Whether a path exists in the manifest.Nr
r�r
r
rrpr
zimanifestdict.__contains__cCr )zjRemove a path from the manifest.

Raises ``KeyError`` if the path is not in the manifest.
Nr
r�r
r
r�__delitem__r
zimanifestdict.__delitem__cCr �z#Iterate over paths in the manifest.Nr
r
r
r
rru r
zimanifestdict.__iter__cCr r�r
r
r
r
r�iterkeysr
zimanifestdict.iterkeyscCr )z'Obtain a list of paths in the manifest.Nr
r
r
r
r�keysr
zimanifestdict.keysNcCr )z�Obtain the set of paths in this manifest but not in another.

``match`` is an optional matcher function to be applied to both
manifests.

Returns a set of paths.
Nr
)�other�matchr
r
r�
filesnotinr
zimanifestdict.filesnotincCr )z7Returns an object implementing the ``idirs`` interface.Nr
r
r
r
r�dirsr
zimanifestdict.dirscCr )z=Returns a bool indicating if a directory is in this manifest.Nr
)�dirr
r
r�hasdirr
zimanifestdict.hasdircCr )z�Generator of paths in manifest satisfying a matcher.

If the matcher has explicit files listed and they don't exist in
the manifest, ``match.bad()`` is called for each missing file.
Nr
)r�r
r
r�walk!r
zimanifestdict.walkFcCr )azFind differences between this manifest and another.

This manifest is compared to ``other``.

If ``match`` is provided, the two manifests are filtered against this
matcher and only entries satisfying the matcher are compared.

If ``clean`` is True, unchanged files are included in the returned
object.

Returns a dict with paths as keys and values of 2-tuples of 2-tuples of
the form ``((node1, flag1), (node2, flag2))`` where ``(node1, flag1)``
represents the node and flags for this manifest and ``(node2, flag2)``
are the same for the other manifest.
Nr
)r�r��cleanr
r
r�diff(r
zimanifestdict.diffcCr )zvSet the flag value for a given path.

Raises ``KeyError`` if the path is not already in the manifest.
Nr
)r��flagr
r
r�setflag9r
zimanifestdict.setflagcCr )z?Obtain the node value for a path or a default value if missing.Nr
)r��defaultr
r
r�get?r
zimanifestdict.getcCr )z>Return the flags value for a path (default: empty bytestring).Nr
r�r
r
rrdBr
zimanifestdict.flagscCr )zReturn a copy of this manifest.Nr
r
r
r
r�copyEr
zimanifestdict.copycCr )z?Returns an iterable of (path, node) for items in this manifest.Nr
r
r
r
r�itemsHr
zimanifestdict.itemscCr )zIdentical to items().Nr
r
r
r
r� iteritemsKr
zimanifestdict.iteritemscCr )z�Returns an iterable of (path, node, flags) for this manifest.

Similar to ``iteritems()`` except items are a 3-tuple and include
flags.
Nr
r
r
r
r�iterentriesNr
zimanifestdict.iterentriescCr )zuObtain the raw data representation for this manifest.

Result is used to create a manifest revision.
Nr
r
r
r
r�textUr
zimanifestdict.textcCr )a�Obtain a delta between this manifest and another given changes.

``base`` in the raw data representation for another manifest.

``changes`` is an iterable of ``(path, to_delete)``.

Returns a 2-tuple containing ``bytearray(self.text())`` and the
delta between ``base`` and this manifest.

If this manifest implementation can't support ``fastdelta()``,
raise ``mercurial.manifest.FastdeltaUnavailable``.
Nr
)�base�changesr
r
r� fastdelta[r
zimanifestdict.fastdeltarG�NF)rrrrror�rlr��__bool__r�rpr�rur�r�r�r�r�r�r�r�r�rdr�r�r�r�r�r�r
r
r
rr��s6

r�c@r)�imanifestrevisionbasez�Base interface representing a single revision of a manifest.

Should not be used as a primary interface: should always be inherited
as part of a larger interface.
cCr )z�Obtain a copy of this manifest instance.

Returns an object conforming to the ``imanifestrevisionwritable``
interface. The instance will be associated with the same
``imanifestlog`` collection as this instance.
Nr
r
r
r
rr�qr
zimanifestrevisionbase.copycCr )z}Obtain the parsed manifest data structure.

The returned object conforms to the ``imanifestdict`` interface.
Nr
r
r
r
rr�yr
zimanifestrevisionbase.readN)rrrrr�r�r
r
r
rr�jsr�c@s>eZdZdZdd�Ze�d�Zd
dd�Zd
dd �Z d
d�Z
dS)�imanifestrevisionstoredz@Interface representing a manifest revision committed to storage.cCr )z"The binary node for this manifest.Nr
r
r
r
rr_�r
zimanifestrevisionstored.nodezAList of binary nodes that are parents for this manifest revision.FcCr )aObtain the manifest data structure representing changes from parent.

This manifest is compared to its 1st parent. A new manifest representing
those differences is constructed.

The returned object conforms to the ``imanifestdict`` interface.
Nr
��shallowr
r
r� readdelta�r
z!imanifestrevisionstored.readdeltacCr )zfCalls either ``read()`` or ``readdelta()``.

The faster of the two options is called.
Nr
r�r
r
r�readfast�r
z imanifestrevisionstored.readfastcCr )zoCalls self.read().find(key)``.

Returns a 2-tuple of ``(node, flags)`` or raises ``KeyError``.
Nr
r4r
r
rr��r
zimanifestrevisionstored.findNr�)rrrrr_rrr|r�r�r�r
r
r
rr��s�

r�c@seZdZdZddd�ZdS)�imanifestrevisionwritablezAInterface representing a manifest revision that can be committed.NcCr )a&Add this revision to storage.

Takes a transaction object, the changeset revision number it will
be associated with, its parent nodes, and lists of added and
removed paths.

If match is provided, storage can choose not to inspect or write out
items that do not match. Storage is still required to be able to provide
the full manifest in the future for any directories written (these
manifests should not be "narrowed on disk").

Returns the binary node of the created revision.
Nr
)r�r�rarb�added�removedr�r
r
r�write�r
zimanifestrevisionwritable.writerG)rrrrr�r
r
r
rr��sr�c@s8eZdZdZe�d�Ze�d�Ze�d�Ze�d�Z e�d�Z
e�d�Zdd �Zd
d�Z
dd
�Zdd�Zdd�Zdd�Zdd�Zdd�Zd<dd�Zd<dd�Zdd�Zdd �Z ! !d=d"d#�Z d>d$d%�Zd&d'�Zd(d)�Zd*d+�Zd,d-�Zd.d/�Zd0d1�Zd2d3�Z d?d4d5�Z!d6d7�Z" d>d8d9�Z# ! ! ! ! !d@d:d;�Z$dS)A�imanifeststoragez$Storage interface for manifest data.�-nodeconstants used by the current repository.ztThe path to the directory this manifest tracks.

The empty bytestring represents the root manifest.
z'An ``ifilerevisionssequence`` instance.z�VFS opener to use to access underlying files used for storage.

TODO this is revlog specific and should not be exposed.
zuWhether generaldelta storage is being used.

TODO this is revlog specific and should not be exposed.
zmDict with cache of fulltexts.

TODO this doesn't feel appropriate for the storage interface.
cCr )z8Obtain the number of revisions stored for this manifest.Nr
r
r
r
rrl�r
zimanifeststorage.__len__cCr )z0Iterate over revision numbers for this manifest.Nr
r
r
r
rru�r
zimanifeststorage.__iter__cCr )zxObtain the revision number given a binary node.

Raises ``error.LookupError`` if the node is not known.
Nr
rvr
r
rrn�r
zimanifeststorage.revcCr )z{Obtain the node value given a revision number.

Raises ``error.LookupError`` if the revision is not known.
Nr
rmr
r
rr_�r
zimanifeststorage.nodecCr )z�Attempt to resolve a value to a node.

Value can be a binary node, hex node, revision number, or a bytes
that can be converted to an integer.

Raises ``error.LookupError`` if a ndoe could not be resolved.
Nr
)�valuer
r
rr6�r
zimanifeststorage.lookupcCr )zqReturns a 2-tuple of parent nodes for a node.

Values will be ``nullid`` if the parent is empty.
Nr
rvr
r
rr|�r
zimanifeststorage.parentscCr r}r
rmr
r
rr~�r
zimanifeststorage.parentrevscCr rr
rmr
r
rr��r
zimanifeststorage.linkrevNcCr )z Obtain fulltext data for a node.Nr
�r_�_dfr
r
rrgr
zimanifeststorage.revisioncCr r�r
r�r
r
rr�r
zimanifeststorage.rawdatacCr )z�Obtain a delta between two revision numbers.

The returned data is the result of ``bdiff.bdiff()`` on the raw
revision data.
Nr
)�rev1�rev2r
r
r�revdiffr
zimanifeststorage.revdiffcCr )zvCompare fulltext to another revision.

Returns True if the fulltext is different from what is stored.
Nr
r�r
r
rr�r
zimanifeststorage.cmpFcCr )ztProduce ``irevisiondelta`` describing revisions.

See the documentation for ``ifiledata`` for more.
Nr
)r/r�r�r�r
r
rr�r
zimanifeststorage.emitrevisionscCr )znProcess a series of deltas for storage.

See the documentation in ``ifilemutation`` for more.
Nr
)r�r�r�r�r�r
r
rr�r
zimanifeststorage.addgroupcCr )z�Obtain the size of tracked data.

Is equivalent to ``len(m.rawdata(node))``.

TODO this method is only used by upgrade code and may be removed.
Nr
rmr
r
r�rawsize+r
zimanifeststorage.rawsizecCr )z�Find minimum revision that must be stripped to strip a linkrev.

See the documentation in ``ifilemutation`` for more.
Nr
r�r
r
rr�3r
zimanifeststorage.getstrippointcCr )zuRemove storage of items starting at a linkrev.

See the documentation in ``ifilemutation`` for more.
Nr
r�r
r
rr�9r
zimanifeststorage.stripcCr )z�Obtain the expected sizes of backing files.

TODO this is used by verify and it should not be part of the interface.
Nr
r
r
r
r� checksize?r
zimanifeststorage.checksizecCr )z�Obtain paths that are backing storage for this manifest.

TODO this is used by verify and there should probably be a better API
for this functionality.
Nr
r
r
r
rr�Er
zimanifeststorage.filescCr )z�Obtain the revision that a revision is delta'd against.

TODO delta encoding is an implementation detail of storage and should
not be exposed to the storage interface.
Nr
rmr
r
r�deltaparentLr
zimanifeststorage.deltaparentcKr )zClone this instance to another.Nr
)r��destr+r
r
r�cloneSr
zimanifeststorage.clonecCr )z/Clear any caches associated with this instance.Nr
)�clear_persisted_datar
r
r�clearcachesVr
zimanifeststorage.clearcachescCr )z.Obtain a manifest storage instance for a tree.Nr
)�dr
r
r�dirlogYr
zimanifeststorage.dirlogc Cr )a�Add a revision to storage.

``m`` is an object conforming to ``imanifestdict``.

``link`` is the linkrev revision number.

``p1`` and ``p2`` are the parent revision numbers.

``added`` and ``removed`` are iterables of added and removed paths,
respectively.

``readtree`` is a function that can be used to read the child tree(s)
when recursively writing the full tree structure when using
treemanifets.

``match`` is a matcher that can be used to hint to storage that not all
paths must be inspected; this is an optimization and can be safely
ignored. Note that the storage must still be able to reproduce a full
manifest including files that did not match.
Nr
) �mr��linkr�r�r�r��readtreer�r
r
rr�\r
zimanifeststorage.addcCr )z�Obtain information about storage for this manifest's data.

See ``ifilestorage.storageinfo()`` for a description of this method.
This one behaves the same way, except for manifest data.
Nr
r�r
r
rr�tr
zimanifeststorage.storageinforG)NFFr�r�r�)%rrrrrr�
nodeconstants�tree�index�opener�
_generaldelta�
fulltextcacherlrurnr_r6r|r~r�rgr�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r�r
r
r
rr��sp������

�
�

��r�c@sLeZdZdZe�d�Zdd�Zddd�Zdd �Z d
d�Z
dd
�Zdd�ZdS)�imanifestlogz�Interface representing a collection of manifest snapshots.

Represents the root manifest in a repository.

Also serves as a means to access nested tree manifests and to cache
tree manifests.
r�cCr )z�Obtain a manifest instance for a given binary node.

Equivalent to calling ``self.get('', node)``.

The returned object conforms to the ``imanifestrevisionstored``
interface.
Nr
rvr
r
rro�r
zimanifestlog.__getitem__TcCr )aKRetrieve the manifest instance for a given directory and binary node.

``node`` always refers to the node of the root manifest (which will be
the only manifest if flat manifests are being used).

If ``tree`` is the empty string, the root manifest is returned.
Otherwise the manifest for the specified directory will be returned
(requires tree manifests).

If ``verify`` is True, ``LookupError`` is raised if the node is not
known.

The returned object conforms to the ``imanifestrevisionstored``
interface.
Nr
)rr_�verifyr
r
rr��r
zimanifestlog.getcCr )aRetrieve an interface to storage for a particular tree.

If ``tree`` is the empty bytestring, storage for the root manifest will
be returned. Otherwise storage for a tree manifest is returned.

TODO formalize interface for returned object.
Nr
)rr
r
r�
getstorage�r
zimanifestlog.getstoragecCr )z-Clear caches associated with this collection.Nr
r
r
r
rr��r
zimanifestlog.clearcachescCr )zvObtain the revision number for a binary node.

Raises ``error.LookupError`` if the node is not known.
Nr
rvr
r
rrn�r
zimanifestlog.revcCr )z8update whatever cache are relevant for the used storage.Nr
)r�r
r
r�
update_caches�r
zimanifestlog.update_cachesN�T)
rrrrrrrror�r
r�rnrr
r
r
rr�s�
rc@seZdZdZdd�ZdS)�ilocalrepositoryfilestoragez�Local repository sub-interface providing access to tracked file storage.

This interface defines how a repository accesses storage for a single
tracked file path.
cCr )ztObtain a filelog for a tracked path.

The returned type conforms to the ``ifilestorage`` interface.
Nr
)�fr
r
r�file�r
z ilocalrepositoryfilestorage.fileN)rrrrrr
r
r
rr
�sr
c@s�eZdZdZe�d�Ze�d�Ze�d�Ze�d�Z e�d�Z
e�d�Ze�d�Ze�d �Z
e�d
�Ze�d�Ze�d�Ze�d
�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Ze�d�Zdd�Zdd�Z dd �Z!d�d"d#�Z"e�d$�Z#e�d%�Z$e�d&�Z%e�d'�Z&e�d(�Z'd�d*d+�Z(d,d-�Z)d.d/�Z*d0d1�Z+d2d3�Z,e,Z-d4d5�Z.d6d7�Z/d8d9�Z0d:d;�Z1d�d<d=�Z2d>d?�Z3d�d@dA�Z4dBdC�Z5dDdE�Z6dFdG�Z7dHdI�Z8dJdK�Z9dLdM�Z:dNdO�Z;dPdQ�Z<d�dRdS�Z=dTdU�Z>dVdW�Z?dXdY�Z@dZd[�ZAd\d]�ZBd^d_�ZCd`da�ZDdbdc�ZEddde�ZFd�dfdg�ZGdhdi�ZHd�djdk�ZIdldm�ZJdndo�ZKd�dpdq�ZLdrds�ZMdtdu�ZNd�dvdw�ZOdxdy�ZPdzd{�ZQd�d|d}�ZRd�d~d�ZSd�d��ZTd�d��ZUd�d��ZVd�d�d��ZWd�d��ZXd�d�d��ZYd�d�d��ZZd�d��Z[d�d��Z\ � ! ! ! ) ) !d�d�d��Z]d�d�d��Z^d�d��Z_d�d��Z` � ! ! ) ) ) )d�d�d��Zad�d��Zbd�d��Zcd�d��Zdd�d�d��Zed�d�d��Zfd�d��Zgd�d��Zhd�d��Zie�d��Zjd�d��Zkd�d��Zld�d�d��Zmd�d��Zn )d�d�d��Zod�d��Zpd!S)��ilocalrepositorymainzzMain interface for local repositories.

This currently captures the reality of things - not how things should be.
zAConstant nodes matching the hash function used by the repository.z;null revision for the hash function used by the repository.z9Set of requirements that this repo is capable of opening.z#Set of requirements this repo uses.atSet of "features" this repository supports.

A "feature" is a loosely-defined term. It can refer to a feature
in the classical sense or can describe an implementation detail
of the repository. For example, a ``readonly`` feature may denote
the repository as read-only. Or a ``revlogfilestore`` feature may
denote that the repository is using revlogs for file storage.

The intent of features is to provide a machine-queryable mechanism
for repo consumers to test for various repository characteristics.

Features are similar to ``requirements``. The main difference is that
requirements are stored on-disk and represent requirements to open the
repository. Features are more run-time capabilities of the repository
and more granular capabilities (which may be derived from requirements).
z1Name of the repoview that is active on this repo.z)VFS used to access the working directory.zcVFS rooted at the .hg directory.

Used to access repository data not in the store.
z�VFS rooted at the store.

Used to access repository data in the store. Typically .hg/store.
But can point elsewhere if the store is shared.
z*Path to the root of the working directory.zPath to the .hg directory.z8The filesystem path that was used to construct the repo.z�A pathauditor for the working directory.

This checks if a path refers to a nested repository.

Operates on the filesystem.
z{A pathauditor for the working directory.

This is like ``auditor`` except it doesn't do filesystem checks.
z-Original ui instance passed into constructor.z#Main ui instance for this instance.z@Path to the .hg directory of the repo this repo was shared from.zA store instance.zPath to the store.zAlias to self.store.join.zPA VFS used to access the cache directory.

Typically .hg/cache.
zjA VFS used to access the cache directory dedicated to working copy

Typically .hg/wcache.
z'Holds sets of revisions to be filtered.zA ``namespaces`` instance.z7The way files copies should be dealt with in this repo.cCr )z$Close the handle on this repository.Nr
r
r
r
rrNr
zilocalrepositorymain.closecCr )z6Obtain an object conforming to the ``peer`` interface.Nr
r
r
r
rrQr
zilocalrepositorymain.peercCr )z+Obtain an unfiltered/raw view of this repo.Nr
r
r
r
r�
unfilteredTr
zilocalrepositorymain.unfilteredNcCr )z'Obtain a named view of this repository.Nr
)r�visibilityexceptionsr
r
r�filteredWr
zilocalrepositorymain.filteredzA store of obsolescence data.z!A handle on the changelog revlog.z|An instance conforming to the ``imanifestlog`` interface.

Provides access to manifests for the repository.
zWorking directory state.z2Matcher patterns for this repository's narrowspec.FcCr )z$Obtain a matcher for the narrowspec.Nr
)r��includeexactr
r
r�narrowmatchkr
z ilocalrepositorymain.narrowmatchcCr )z*Define the narrowspec for this repository.Nr
)�newincludes�newexcludesr
r
r�
setnarrowpatsnr
z"ilocalrepositorymain.setnarrowpatscCr )zTry to resolve a changectx.Nr
��changeidr
r
rroqr
z ilocalrepositorymain.__getitem__cCr )zWhether a changeset exists.Nr
rr
r
rrptr
z!ilocalrepositorymain.__contains__cCr )zAlways returns True.Tr
r
r
r
rr�w�z ilocalrepositorymain.__nonzero__cCr )z-Returns the number of changesets in the repo.Nr
r
r
r
rrl}r
zilocalrepositorymain.__len__cCr )z(Iterate over revisions in the changelog.Nr
r
r
r
rru�r
zilocalrepositorymain.__iter__cGr )z5Evaluate a revset.

Emits revisions.
Nr
��exprrLr
r
rr{�r
zilocalrepositorymain.revscGr )z?Evaluate a revset.

Emits changectx instances.
Nr
rr
r
r�set�r
zilocalrepositorymain.setcCr )z1Find revisions matching one of the given revsets.Nr
)�specs�user�
localaliasr
r
r�anyrevs�r
zilocalrepositorymain.anyrevscCr )z8Returns a string representing the location of this repo.Nr
r
r
r
rr�r
zilocalrepositorymain.urlcKr )zCall a hook.Nr
)r�throwrLr
r
r�hook�r
zilocalrepositorymain.hookcCr )z Return a mapping of tag to node.Nr
r
r
r
r�tags�r
zilocalrepositorymain.tagscCr )zReturn the type of a given tag.Nr
)�tagnamer
r
r�tagtype�r
zilocalrepositorymain.tagtypecCr )z*Return a list of tags ordered by revision.Nr
r
r
r
r�tagslist�r
zilocalrepositorymain.tagslistcCr )z'Return the tags associated with a node.Nr
rvr
r
r�nodetags�r
zilocalrepositorymain.nodetagscCr )z<Return the list of bookmarks pointing to the specified node.Nr
rvr
r
r�
nodebookmarks�r
z"ilocalrepositorymain.nodebookmarkscCr )z3Return a mapping of branch to heads in that branch.Nr
r
r
r
rr �r
zilocalrepositorymain.branchmapcCrFrGr
r
r
r
r�revbranchcache�rJz#ilocalrepositorymain.revbranchcachecCr )aExtension point for caches for new nodes.

Multiple consumers are expected to need parts of the changelogrevision,
so it is provided as optimization to avoid duplicate lookups. A simple
cache would be fragile when other revisions are accessed, too.Nr
)rn�changelogrevisionr
r
r�register_changeset�sz'ilocalrepositorymain.register_changesetcCr )z'Return the tip node for a given branch.Nr
)� branchtip�
ignoremissingr
r
rr.�r
zilocalrepositorymain.branchtipcCr )z Resolve the node for a revision.Nr
r4r
r
rr6�r
zilocalrepositorymain.lookupcCr )z=Look up the branch name of the given revision or branch name.Nr
r4r
r
r�lookupbranch�r
z!ilocalrepositorymain.lookupbranchcCr )zXDetermine whether a series of nodes is known.

Returns a list of bools.
Nr
r.r
r
rr0�r
zilocalrepositorymain.knowncCr )z Whether the repository is local.Tr
r
r
r
rr�rzilocalrepositorymain.localcCr )z2Whether the repository is a publishing repository.Nr
r
r
r
r�
publishing�r
zilocalrepositorymain.publishingcCrFrGr
r
r
r
r�cancopy�rJzilocalrepositorymain.cancopycCr )z&The type of shared repository or None.Nr
r
r
r
r�shared�r
zilocalrepositorymain.sharedcGr )z.Calls self.vfs.reljoin(self.root, f, *insidef)Nr
)r�insidefr
r
r�wjoin�r
zilocalrepositorymain.wjoincCr )z.Set the parent nodes of the working directory.Nr
)r�r�r
r
r�
setparents�r
zilocalrepositorymain.setparentscCr )z-Obtain a filectx for the given file revision.Nr
)r�r�fileidr
r
r�filectx�r
zilocalrepositorymain.filectxcCr )z7Obtain the current working directory from the dirstate.Nr
r
r
r
r�getcwd�r
zilocalrepositorymain.getcwdcCr )z#Obtain the relative path to a file.Nr
)r�cwdr
r
r�pathto�r
zilocalrepositorymain.pathtocCrFrGr
)r�fltrr
r
r�
adddatafilter�rJz"ilocalrepositorymain.adddatafiltercCr )z*Read a file from wvfs, using data filters.Nr
)�filenamer
r
r�wread�r
zilocalrepositorymain.wreadcKr )z5Write data to a file in the wvfs, using data filters.Nr
)r>�datard�backgroundcloser+r
r
r�wwrite�r
zilocalrepositorymain.wwritecCr )z9Resolve data for writing to the wvfs, using data filters.Nr
)r>r@r
r
r�
wwritedata�r
zilocalrepositorymain.wwritedatacCr )z0Obtain the current transaction instance or None.Nr
r
r
r
r�currenttransaction�r
z'ilocalrepositorymain.currenttransactioncCr )z2Open a new transaction to write to the repository.Nr
)�desc�reportr
r
rr��r
z ilocalrepositorymain.transactioncCr )z=Returns a list of (vfs, path) for files to undo transactions.Nr
r
r
r
r� undofiles�r
zilocalrepositorymain.undofilescCr )z%Roll back an interrupted transaction.Nr
r
r
r
r�recover�r
zilocalrepositorymain.recovercCr )z7Undo the last transaction.

DANGEROUS.
Nr
)�dryrun�forcer
r
r�rollback�r
zilocalrepositorymain.rollbackcCr )zWarm repo caches.Nr
)r��full�cachesr
r
r�updatecaches�r
z!ilocalrepositorymain.updatecachescCr )z6Invalidate cached data due to the repository mutating.Nr
r
r
r
r�invalidatecachesr
z%ilocalrepositorymain.invalidatecachescCrFrGr
r
r
r
r�invalidatevolatilesetsrJz+ilocalrepositorymain.invalidatevolatilesetscCr )zInvalidate the dirstate.Nr
r
r
r
r�invalidatedirstater
z'ilocalrepositorymain.invalidatedirstatecCrFrGr
)�clearfilecacher
r
r�
invalidate
rJzilocalrepositorymain.invalidatecCrFrGr
r
r
r
r�
invalidateall
rJz"ilocalrepositorymain.invalidateallTcCr )z5Lock the repository store and return a lock instance.Nr
��waitr
r
r�lockr
zilocalrepositorymain.lockcCr )z+Lock the non-store parts of the repository.Nr
rUr
r
r�wlockr
zilocalrepositorymain.wlockcCr )z&Return the wlock if it's held or None.Nr
r
r
r
r�currentwlockr
z!ilocalrepositorymain.currentwlockcCrFrGr
)�wctxr��status�failr
r
r�checkcommitpatternsrJz(ilocalrepositorymain.checkcommitpatternsr�cCr )z%Add a new revision to the repository.Nr
)r�r �dater�rJ�editor�extrar
r
r�commitr
zilocalrepositorymain.commitcCr )z.Commit a commitctx instance to the repository.Nr
)�ctxr�origctxr
r
r� commitctx'r
zilocalrepositorymain.commitctxcCr )z;Inform the repository that nodes are about to be destroyed.Nr
r
r
r
r�
destroying*r
zilocalrepositorymain.destroyingcCr )z5Inform the repository that nodes have been destroyed.Nr
r
r
r
r� destroyed-r
zilocalrepositorymain.destroyed�.cCr )z,Convenience method to call repo[x].status().Nr
)r�r�r��ignoredr��unknown�listsubreposr
r
rr[0r
zilocalrepositorymain.statuscCrFrGr
)�psr
r
r�addpostdsstatus;rJz$ilocalrepositorymain.addpostdsstatuscCrFrGr
r
r
r
r�postdsstatus>rJz!ilocalrepositorymain.postdsstatuscCrFrGr
r
r
r
r�clearpostdsstatusArJz&ilocalrepositorymain.clearpostdsstatuscCr )z(Obtain list of nodes that are DAG heads.Nr
)ryr
r
rr-Dr
zilocalrepositorymain.headscCrFrGr
)�branchry�closedr
r
r�branchheadsGrJz ilocalrepositorymain.branchheadscCrFrGr
r.r
r
rrDJrJzilocalrepositorymain.branchescCrFrGr
rAr
r
rrCMrJzilocalrepositorymain.betweencCrFrGr
)�pushopr
r
r� checkpushPrJzilocalrepositorymain.checkpushzutil.hooks instance.cCrFrGr
r7r
r
rr:UrJzilocalrepositorymain.pushkeycCrFrGr
r1r
r
rr3XrJzilocalrepositorymain.listkeyscCrFrGr
r#r
r
rr)[rJz"ilocalrepositorymain.debugwireargscCrFrGr
)r�r
r
r�savecommitmessage^rJz&ilocalrepositorymain.savecommitmessagecCrFrGr
)�kind�categoryr��computerrd�replacer
r
r�register_sidedata_computerasz/ilocalrepositorymain.register_sidedata_computercCrFrGr
)rvr
r
r�register_wanted_sidedatafrJz-ilocalrepositorymain.register_wanted_sidedatarGr�)FNr�r�)FF)NFNr)r�NNNFFN)rgNNFFFFr�r>)qrrrrrrrr�� supported�requirements�features�
filtername�wvfs�vfs�svfs�rootr��origroot�auditor�nofsauditor�baseuir�
sharedpath�store�spath�sjoin�cachevfs� wcachevfs�filteredrevcache�names�filecopiesmoderrrr�obsstore� changelog�manifestlog�dirstate�
narrowpatsrrrorpr�r�rlrur{rr"rr$r%r'r(r)r*r r+r-r.r6r0r0rr1r2r3r5r6r8r9r;r=r?rBrCrDr�rGrHrKrNrOrPrQrSrTrWrXrYr]rardrerfr[rlrmrnr-rqrDrCrs�prepushoutgoinghooksr:r3r)rtryrzr
r
r
rr�sL����������
�� ��
�

���
�

�
�

�

�rc@rR)�completelocalrepositoryz*Complete interface for a local repository.NrTr
r
r
rr�jsr�c@sHeZdZdZdd�Zdd�Zdd�Zdd �Zd
d�Zdd
�Z dd�Z
dS)�iwireprotocolcommandcachera�Represents a caching backend for wire protocol commands.

Wire protocol version 2 supports transparent caching of many commands.
To leverage this caching, servers can activate objects that cache
command responses. Objects handle both cache writing and reading.
This interface defines how that response caching mechanism works.

Wire protocol version 2 commands emit a series of objects that are
serialized and sent to the client. The caching layer exists between
the invocation of the command function and the sending of its output
objects to an output layer.

Instances of this interface represent a binding to a cache that
can serve a response (in place of calling a command function) and/or
write responses to a cache for subsequent use.

When a command request arrives, the following happens with regards
to this interface:

1. The server determines whether the command request is cacheable.
2. If it is, an instance of this interface is spawned.
3. The cacher is activated in a context manager (``__enter__`` is called).
4. A cache *key* for that request is derived. This will call the
instance's ``adjustcachekeystate()`` method so the derivation
can be influenced.
5. The cacher is informed of the derived cache key via a call to
``setcachekey()``.
6. The cacher's ``lookup()`` method is called to test for presence of
the derived key in the cache.
7. If ``lookup()`` returns a hit, that cached result is used in place
of invoking the command function. ``__exit__`` is called and the instance
is discarded.
8. The command function is invoked.
9. ``onobject()`` is called for each object emitted by the command
function.
10. After the final object is seen, ``onfinished()`` is called.
11. ``__exit__`` is called to signal the end of use of the instance.

Cache *key* derivation can be influenced by the instance.

Cache keys are initially derived by a deterministic representation of
the command request. This includes the command name, arguments, protocol
version, etc. This initial key derivation is performed by CBOR-encoding a
data structure and feeding that output into a hasher.

Instances of this interface can influence this initial key derivation
via ``adjustcachekeystate()``.

The instance is informed of the derived cache key via a call to
``setcachekey()``. The instance must store the key locally so it can
be consulted on subsequent operations that may require it.

When constructed, the instance has access to a callable that can be used
for encoding response objects. This callable receives as its single
argument an object emitted by a command function. It returns an iterable
of bytes chunks representing the encoded object. Unless the cacher is
caching native Python objects in memory or has a way of reconstructing
the original Python objects, implementations typically call this function
to produce bytes from the output objects and then store those bytes in
the cache. When it comes time to re-emit those bytes, they are wrapped
in a ``wireprototypes.encodedresponse`` instance to tell the output
layer that they are pre-encoded.

When receiving the objects emitted by the command function, instances
can choose what to do with those objects. The simplest thing to do is
re-emit the original objects. They will be forwarded to the output
layer and will be processed as if the cacher did not exist.

Implementations could also choose to not emit objects - instead locally
buffering objects or their encoded representation. They could then emit
a single "coalesced" object when ``onfinished()`` is called. In
this way, the implementation would function as a filtering layer of
sorts.

When caching objects, typically the encoded form of the object will
be stored. Keep in mind that if the original object is forwarded to
the output layer, it will need to be encoded there as well. For large
output, this redundant encoding could add overhead. Implementations
could wrap the encoded object data in ``wireprototypes.encodedresponse``
instances to avoid this overhead.
cCr )zCMarks the instance as active.

Should return self.
Nr
r
r
r
r� __enter__�r
z$iwireprotocolcommandcacher.__enter__cCr )z�Called when cacher is no longer used.

This can be used by implementations to perform cleanup actions (e.g.
disconnecting network sockets, aborting a partially cached response.
Nr
)�exctype�excvalue�exctbr
r
r�__exit__�r
z#iwireprotocolcommandcacher.__exit__cCr )arInfluences cache key derivation by adjusting state to derive key.

A dict defining the state used to derive the cache key is passed.

Implementations can modify this dict to record additional state that
is wanted to influence key derivation.

Implementations are *highly* encouraged to not modify or delete
existing keys.
Nr
r�r
r
r�adjustcachekeystate�r
z.iwireprotocolcommandcacher.adjustcachekeystatecCr )a~Record the derived cache key for this request.

Instances may mutate the key for internal usage, as desired. e.g.
instances may wish to prepend the repo name, introduce path
components for filesystem or URL addressing, etc. Behavior is up to
the cache.

Returns a bool indicating if the request is cacheable by this
instance.
Nr
r4r
r
r�setcachekey�r
z&iwireprotocolcommandcacher.setcachekeycCr )a�Attempt to resolve an entry in the cache.

The instance is instructed to look for the cache key that it was
informed about via the call to ``setcachekey()``.

If there's no cache hit or the cacher doesn't wish to use the cached
entry, ``None`` should be returned.

Else, a dict defining the cached result should be returned. The
dict may have the following keys:

objs
An iterable of objects that should be sent to the client. That
iterable of objects is expected to be what the command function
would return if invoked or an equivalent representation thereof.
Nr
r
r
r
rr6�r
z!iwireprotocolcommandcacher.lookupcCr )aOCalled when a new object is emitted from the command function.

Receives as its argument the object that was emitted from the
command function.

This method returns an iterator of objects to forward to the output
layer. The easiest implementation is a generator that just
``yield obj``.
Nr
)�objr
r
r�onobject�r
z#iwireprotocolcommandcacher.onobjectcCr )z�Called after all objects have been emitted from the command function.

Implementations should return an iterator of objects to forward to
the output layer.

This method can be a generator.
Nr
r
r
r
r�
onfinishedr
z%iwireprotocolcommandcacher.onfinishedN)rrrrr�r�r�r�r6r�r�r
r
r
rr�psRr�N)C�
__future__r�i18nr�rrr� REPO_FEATURE_REVLOG_FILE_STORAGE�REPO_FEATURE_SHARED_STORAGE�REPO_FEATURE_LFS�REPO_FEATURE_STREAM_CLONE�REPO_FEATURE_SIDE_DATA�!REPO_FEATURE_SHALLOW_FILE_STORAGE�REVISION_FLAG_CENSORED�REVISION_FLAG_ELLIPSIS�REVISION_FLAG_EXTSTORED�REVISION_FLAG_HASCOPIESINFO�REVISION_FLAGS_KNOWNr��CG_DELTAMODE_PREV�CG_DELTAMODE_FULL�CG_DELTAMODE_P1�CACHE_BRANCHMAP_ALL�CACHE_BRANCHMAP_SERVED�CACHE_CHANGELOG_CACHE�CACHE_FULL_MANIFEST�CACHE_FILE_NODE_TAGS�CACHE_MANIFESTLOG_CACHE�CACHE_REV_BRANCH�CACHE_TAGS_DEFAULT�CACHE_TAGS_SERVED�CACHES_DEFAULT�
CACHES_ALLr��CACHES_POST_CLONE�discard� Interfacerrrr@rKrOrSrU�implementer�objectrr]r`rkrtr�r�r�r�r�r�r�r�r�rr
rr�r�r
r
r
r�<module>s�������
0Z!:H4eksC P=
�