HEX
Server: LiteSpeed
System: Linux s787.bom1.mysecurecloudhost.com 4.18.0-477.13.1.lve.el8.x86_64 #1 SMP Thu Jun 1 16:40:47 EDT 2023 x86_64
User: mobilech (5348)
PHP: 8.1.34
Disabled: NONE
$ pwd: /opt/saltstack/salt/lib/python3.10/site-packages/git/index/__pycache__/
Upload Files
File: //opt/saltstack/salt/lib/python3.10/site-packages/git/index/__pycache__/base.cpython-310.pyc
o

;j1��@sdZgd�ZddlZddlZddlZddlmZddlZddlm	Z
ddlmZddl
Z
ddlZddlZddlmZddlmZddlmZmZddlmZdd	lmZmZmZmZdd
lm Z m!Z!m"Z"m#Z#m$Z$ddl%m&Z&ddl'm(Z(m)Z)m*Z*m+Z+m,Z,m-Z-m.Z.m/Z/d
dl0m1Z1m2Z2m3Z3m4Z4m5Z5m6Z6m7Z7m8Z8d
dl9m:Z:m;Z;m<Z<d
dl=m>Z>m?Z?m@Z@mAZAddlBmCZCmDZDmEZEmFZFmGZGmHZHmIZImJZJmKZKmLZLmMZMmNZNmOZOmPZPddlQmRZRmSZSeNr�ddl
mTZTddlUmVZVddlWmXZXePe$e!eYeZfZ[ej\deSdeGeYddffdd��Z]Gdd�de)ej^e&�Z_dS)z�Module containing :class:`IndexFile`, an Index implementation facilitating all kinds
of index manipulations such as querying and merging.)�	IndexFile�
CheckoutError�	StageType�N)�BytesIO)�S_ISLNK)�IStream)�MemoryDB)�defenc�force_bytes)r�GitCommandError�GitError�InvalidGitRepositoryError)�Blob�Commit�Object�	Submodule�Tree)�Serializable)�Actor�	LazyMixin�LockedFD�join_path_native�file_contents_ro�to_native_path_linux�unbare_repo�
to_bin_sha�)�S_IFGITLINK�aggressive_tree_merge�	entry_key�
read_cache�run_commit_hook�stat_mode_to_index_mode�write_cache�write_tree_from_cache)�BaseIndexEntry�
IndexEntryr)�TemporaryFileSwap�post_clear_cache�
default_index�git_working_dir)�Any�BinaryIO�Callable�Dict�	Generator�IO�Iterable�Iterator�List�NoReturn�Sequence�
TYPE_CHECKING�Tuple�Union)�Literal�PathLike)�Popen)�	Reference)�Repo�	directory�returnc	cs��tjdkr%tj|d�\}}t�|�z|VWt�|�dSt�|�wtj|d��
}|jVWd�dS1s;wYdS)a$Create a named temporary file git subprocesses can open, deleting it afterward.

    :param directory:
        The directory in which the file is created.

    :return:
        A context manager object that creates the file and provides its name on entry,
        and deletes it on exit.
    �win32)�dirN)	�sys�platform�tempfileZmkstemp�os�close�removeZNamedTemporaryFile�name)r>�fdrH�ctx�rK�B/opt/saltstack/salt/lib/python3.10/site-packages/git/index/base.py�$_named_temporary_file_for_subprocessWs�


"�rMcseZdZdZdZdZ	eZ	d�dddeedfddfd	d
�Z	de
ddf�fdd
�Zdefdd�Ze
defdd��Zd�dd�Zdeddfdd�Zdeefdd�Zd�dededdfdd�Z		d�dedefdeddfdd�Zeed�ded edefddfd!d"���Zeddd#ee
efddfd$d%��Zeddd&ed'eddfd(d)��Z e!d*dd+e"ede#efd,d-��Z$	.d�d/d0d1ed2ed3e%d4e&fd5e%eeegdfd6edede
ffd7d8�Z'd9d:�fd;e%e(e)e*fgefde#e(e)e*ffd<d=�Z+de,eee(e)e*fffd>d?�Z-ed@ee.ee)fde(ee)ffdAdB��Z/dCe#e*ddfdDdE�Z0d�dFdG�Z1defdHdI�Z2dJeeedKfdeeedKffdLdM�Z3dNedefdOdP�Z4dQeee"eee*e.dRffde(eeee.ffdSdT�Z5d1ed5e%de.fdUdV�Z6e!e7d+ee
dWee%dfd5e%dXee.dee.f
dYdZ���Z8d.d[d:�dd.dfdQeee"eee*e.dRffd\ed5e%dWee%d4efdfd]ed^edee.fd_d`�Z9dQeee"eee.e*e:ffdeefdadb�Z;ee	d�dQeee"eee*e.dRffdced'edee
fddde���Z<ee	d�dQeee"eee*e.dRffdfed'edee(e
e
ffdgdh���Z=		.						d�die
djeee>dfdkedlede?fdmede?fdnee@j@e
dfdoee@j@e
dfdpedqedrde>fdsdt�ZAdie
ddfdudv�ZBd�dwdx�ZCde
fdydz�ZDde
fd{d|�ZEd�d/d}d~edeFfdd��ZGeddd�d:�fd+edeHefd\ed5e%d'edede#ee"eff
d�d���ZIe	�			d�d�ee>d�e
fdced+edeHefdked'eddfd�d���ZJeKjLddfd�eeMeKjNjLd�d�e
dfd+eeeee(ed4fdfd�ed'edeKjOeKjPf
�fd�d��
ZQ�ZRS)�ra�An Index that can be manipulated using a native implementation in order to save
    git command function calls wherever possible.

    This provides custom merging facilities allowing to merge without actually changing
    your index or your working tree. This way you can perform your own test merges based
    on the index only without having to deal with the working copy. This is useful in
    case of partial working trees.

    Entries:

        The index contains an entries dict whose keys are tuples of type
        :class:`~git.index.typ.IndexEntry` to facilitate access.

        You may read the entries dict or manipulate it using IndexEntry instance, i.e.::

            index.entries[index.entry_key(index_entry_instance)] = index_entry_instance

    Make sure you use :meth:`index.write() <write>` once you are done manipulating the
    index directly before operating on it using the git command.
    )�repo�version�entries�_extension_data�
_file_path�NrNr=�	file_pathr?cCs&||_|j|_d|_|p|��|_dS)aInitialize this Index instance, optionally from the given `file_path`.

        If no `file_path` is given, we will be created from the current index file.

        If a stream is not given, the stream will be initialized from the current
        repository's index on demand.
        �N)rN�_VERSIONrOrQ�_index_pathrR)�selfrNrTrKrKrL�__init__�szIndexFile.__init__�attrc	s�|dkr8z
t�|jtj�}Wn
tyi|_YdSwzt|ddd�}Wt�|�nt�|�w|�|�dSt	��
|�dS)NrPT)�streamZ
allow_mmap)rE�openrR�O_RDONLY�OSErrorrPrrF�_deserialize�super�_set_cache_)rXrZrIr[��	__class__rKrLra�s�zIndexFile._set_cache_cCs|jjrt|jjd�Std��)N�indexz)No git directory given to join index path)rN�git_dirrr�rXrKrKrLrW�szIndexFile._index_pathcCs|jS)z3:return: Path to the index file we are representing)rRrfrKrKrL�path�szIndexFile.pathcCs z|`WdStyYdSw)z6Safely clear the entries cache so it can be recreated.N)rP�AttributeErrorrfrKrKrL�_delete_entries_cache�s

�zIndexFile._delete_entries_cacher[cCst|�\|_|_|_}|S)zFInitialize this instance with index values read from the given stream.)r rOrPrQ)rXr[Z_conten_sharKrKrLr_�szIndexFile._deserializecCst|j��dd�d�S)zK:return: List of entries, in a sorted fashion, first by path, then by stagecSs|j|jfS�N�rg�stage��erKrKrL�<lambda>�sz+IndexFile._entries_sorted.<locals>.<lambda>)�key)�sortedrP�valuesrfrKrKrL�_entries_sorted�szIndexFile._entries_sortedF�ignore_extension_datacCs&|��}|j}|rd}t|||�|Srj)rsrQr#)rXr[rtrPZextension_datarKrKrL�
_serialize�szIndexFile._serializecCsj|jt|p|j�}|jddd�}z|�||�Wnty%|���w|��|dur3||_dSdS)a�Write the current state to our file path or to the given one.

        :param file_path:
            If ``None``, we will write to our stored file path from which we have been
            initialized. Otherwise we write to the given file path. Please note that
            this will change the `file_path` of this index to the one you gave.

        :param ignore_extension_data:
            If ``True``, the TREE type extension data read in the index will not be
            written to disk. NOTE that no extension data is actually written. Use this
            if you have altered the index and would like to use
            :manpage:`git-write-tree(1)` afterwards to create a tree representing your
            written changes. If this data is present in the written index,
            :manpage:`git-write-tree(1)` will instead write the stored/cached tree.
            Alternatively, use :meth:`write_tree` to handle this case automatically.
        T)�writer[N)rPrrRr\ru�
BaseExceptionZrollback�commit)rXrTrtZlfdr[rKrKrLrv�s�
�zIndexFile.write�rhs�basecCs6gd�}|dur
|�|�|�|�|jj�|�|S)a�Merge the given `rhs` treeish into the current index, possibly taking
        a common base treeish into account.

        As opposed to the :func:`from_tree` method, this allows you to use an already
        existing tree as the left side of the merge.

        :param rhs:
            Treeish reference pointing to the 'other' side of the merge.

        :param base:
            Optional treeish reference pointing to the common base of `rhs` and this
            index which equals lhs.

        :return:
            self (containing the merge and possibly unmerged entries in case of
            conflicts)

        :raise git.exc.GitCommandError:
            If there is a merge conflict. The error will be raised at the first
            conflicting path. If you want to have proper merge resolution to be done by
            yourself, you have to commit the changed index (or make a valid tree from
            it) and retry with a three-way :meth:`index.from_tree <from_tree>` call.
        )�--aggressivez-iz-mN)�appendrN�git�	read_tree)rXryrz�argsrKrKrL�
merge_tree�s

zIndexFile.merge_tree�tree_shacGsNdd�|D�}t|j|�}||�}ttdd�|D�dd�|D���}||_|S)aMerge the given treeish revisions into a new index which is returned.

        This method behaves like ``git-read-tree --aggressive`` when doing the merge.

        :param repo:
            The repository treeish are located in.

        :param tree_sha:
            20 byte or 40 byte tree sha or tree objects.

        :return:
            New :class:`IndexFile` instance. Its path will be undefined.
            If you intend to write such a merged Index, supply an alternate
            ``file_path`` to its :meth:`write` method.
        cSsg|]}tt|���qSrK)r�str)�.0�trKrKrL�
<listcomp>4�z!IndexFile.new.<locals>.<listcomp>css�|]	}|j|jfVqdSrjrk�r�rnrKrKrL�	<genexpr>;s�z IndexFile.new.<locals>.<genexpr>css�|]}t�|�VqdSrj)r&�	from_baser�rKrKrLr�<s�)r�odb�dict�ziprP)�clsrNr�Ztree_sha_bytesZbase_entries�instrPrKrKrL�new#s��z
IndexFile.new�treeish�kwargsc	Os�t|�dkst|�dkrtdt|���g}t|�dkr&|�d�|�d�t|j��G}|�d|�|�|�tt|jd���"|jj	|i|��|||�}|j
|Wd	�Wd	�S1sewYWd	�d	S1suwYd	S)
a�Merge the given treeish revisions into a new index which is returned.
        The original index will remain unaltered.

        :param repo:
            The repository treeish are located in.

        :param treeish:
            One, two or three :class:`~git.objects.tree.Tree` objects,
            :class:`~git.objects.commit.Commit`\s or 40 byte hexshas.

            The result changes according to the amount of trees:

            1. If 1 Tree is given, it will just be read into a new index.
            2. If 2 Trees are given, they will be merged into a new index using a two
               way merge algorithm. Tree 1 is the 'current' tree, tree 2 is the 'other'
               one. It behaves like a fast-forward.
            3. If 3 Trees are given, a 3-way merge will be performed with the first tree
               being the common ancestor of tree 2 and tree 3. Tree 2 is the 'current'
               tree, tree 3 is the 'other' one.

        :param kwargs:
            Additional arguments passed to :manpage:`git-read-tree(1)`.

        :return:
            New :class:`IndexFile` instance. It will point to a temporary index location
            which does not exist anymore. If you intend to write such a merged Index,
            supply an alternate ``file_path`` to its :meth:`write` method.

        :note:
            In the three-way merge case, ``--aggressive`` will be specified to
            automatically resolve more cases in a commonly correct manner. Specify
            ``trivial=True`` as a keyword argument to override that.

            As the underlying :manpage:`git-read-tree(1)` command takes into account the
            current index, it will be temporarily moved out of the way to prevent any
            unexpected interference.
        r�z.Please specify between 1 and 3 treeish, got %irz--resetr{z--index-output=%srdN)�len�
ValueErrorr|rMre�extendr'rr}r~rP)r�rNr�r��arg_listZ	tmp_indexrdrKrKrL�	from_treeCs$'



��"�zIndexFile.from_treerX�pathsc	csR�dtdtfdd�}t|jj�}|tj}|D]�}t�|�}t�	|�s)t�
||�}zt�|�}Wn	ty9Ynwt
|j�rG|�|d�Vqtj�|�swd|vsYd|vsYd|vrwt�|�}||vrw|�t�|��D]}	t|	��|d�Vqjqztj||d	�D]\}
}}|D]
}
t�
|
�|d�|
�Vq�qWqty�|�|d�VYqwd
S)a=Expand the directories in list of paths to the corresponding paths
        accordingly.

        :note:
            git will add items multiple times even if a glob overlapped with manually
            specified paths or if paths where specified multiple times - we respect that
            and do not prune.
        rnr?cSs|�rjrKrmrKrKrL�	raise_exc�sz/IndexFile._iter_expand_paths.<locals>.raise_exc��?�*�[)�onerrorN)�	Exceptionr4r�rN�working_tree_dirrE�sep�fspath�osp�isabs�join�lstatr^r�st_mode�replacerg�exists�glob�_iter_expand_paths�walk)rXr�r��rZrsrgZabs_path�stZresolved_paths�f�rootZ_dirs�filesZ	rela_filerKrKrLr��s@�


�
$
����zIndexFile._iter_expand_pathsT�procr;�filepath�item�fmakeexc.�	fprogress�read_from_stdoutc	
Cs�||d|�d}|jdur0z
|j�d|�t��Wnty*}z|�|�d}~ww|j��|r>|jdur>|j����}||d|�|S)a�Write path to ``proc.stdin`` and make sure it processes the item, including
        progress.

        :return:
            stdout string

        :param read_from_stdout:
            If ``True``, ``proc.stdout`` will be read after the item was sent to stdin.
            In that case, it will return ``None``.

        :note:
            There is a bug in :manpage:`git-update-index(1)` that prevents it from
            sending reports just in time. This is why we have a version that tries to
            read stdout and one which doesn't. In fact, the stdout is not important as
            the piped-in files are processed anyway and just in time.

        :note:
            Newlines are essential here, git's behaviour is somewhat inconsistent on
            this depending on the version, hence we try our best to deal with newlines
            carefully. Usually the last newline will not be sent, instead we will close
            stdin to break the pipe.
        FNz%s
T)	�stdinrv�encoder	�IOError�flush�stdout�readline�strip)	rXr�r�r�r�r�r��rvalrnrKrKrL�_write_path_to_stdin�s
��
zIndexFile._write_path_to_stdincCsdS)NTrK�r�rKrKrLro��zIndexFile.<lambda>�	predicateccsB�|j��D]}|�|j�}|j|_|j|f}||�r|VqdS)a�
        :return:
            Iterator yielding tuples of :class:`~git.objects.blob.Blob` objects and
            stages, tuple(stage, Blob).

        :param predicate:
            Function(t) returning ``True`` if tuple(stage, Blob) should be yielded by
            the iterator. A default filter, the :class:`~git.index.typ.BlobFilter`, allows you
            to yield blobs only if they match a given list of paths.
        N)rPrrZto_blobrN�sizerl)rXr��entry�blob�outputrKrKrL�
iter_blobs�s�

��zIndexFile.iter_blobscCsddtttfdtfdd�}i}|�|�D]\}}|�|jg��||f�q|��D]}|�	�q)|S)a�
        :return:
            Dict(path : list(tuple(stage, Blob, ...))), being a dictionary associating a
            path in the index with a list containing sorted stage/blob pairs.

        :note:
            Blobs that have been removed in one side simply do not exist in the given
            stage. That is, a file removed on the 'other' branch whose entries are at
            stage 3 will not have a stage 3 entry.
        r�r?cSs|ddkS)NrrKr�rKrKrL�is_unmerged_blobsz2IndexFile.unmerged_blobs.<locals>.is_unmerged_blob)
r7rr�boolr��
setdefaultrgr|rr�sort)rXr�Zpath_maprlr��linerKrKrL�unmerged_blobs
s
zIndexFile.unmerged_blobsr�cGst|�Srj)r)r�r�rKrKrLr"szIndexFile.entry_keyr�c
Csr|D]4}|jdf}||jvrtdt|j���dD]}z	|j|j|f=Wqty-Yqwt�|�|j|<q|S)amResolve the blobs given in blob iterator.

        This will effectively remove the index entries of the respective path at all
        non-null stages and add the given blob as new stage null blob.

        For each path there may only be one blob, otherwise a :exc:`ValueError` will be
        raised claiming the path is already at stage 0.

        :raise ValueError:
            If one of the blobs already existed at stage 0.

        :return:
            self

        :note:
            You will have to write the index manually once you are done, i.e.
            ``index.resolve_blobs(blobs).write()``.
        rz!Path %r already exists at stage 0)rrSr�)rgrPr�r��KeyErrorr&�	from_blob)rXr�r�Zstage_null_keyrlrKrKrL�
resolve_blobs&s

�zIndexFile.resolve_blobscCs|��|S)aReread the contents of our index file, discarding all cached information
        we might have.

        :note:
            This is a possibly dangerous operations as it will discard your changes to
            :attr:`index.entries <entries>`.

        :return:
            self
        )rirfrKrKrL�updateMszIndexFile.updatecCsVt�}|��}t||tdt|���\}}|�|��|jj�t	|j|dd�}||_
|S)aOWrite this index to a corresponding :class:`~git.objects.tree.Tree` object
        into the repository's object database and return it.

        :return:
            :class:`~git.objects.tree.Tree` object representing this index.

        :note:
            The tree will be written even if one or more objects the tree refers to does
            not yet exist in the object database. This could happen if you added entries
            to the index directly.

        :raise ValueError:
            If there are no entries in the cache.

        :raise git.exc.UnmergedEntriesError:
        rr��rg)rrsr$�slicer�Zstream_copyZsha_iterrNr�r�_cache)rXZmdbrP�binshaZ
tree_itemsZ	root_treerKrKrL�
write_tree\szIndexFile.write_treerzgit_diff.DiffablecCs,z|�|�|��W|StyY|Swrj)�poprd�
IndexError)rXrrKrKrL�_process_diff_args|s��zIndexFile._process_diff_argsrgcCs�t�|�s|S|jjrtd��t�|��t|jj��s%t	d||jjf��t
j�||jj�}t
�
|��t
j�rB|�t
j�sB|t
j7}|S)z�
        :return:
            Version of path relative to our git directory or raise :exc:`ValueError` if
            it is not within our git directory.

        :raise ValueError:
        zrequire non-bare repositoryz/Absolute path %r is not in git repository at %r)r�r�rNZbarer
�normpath�
startswithr�r�r�rErg�relpathr��endswithr�)rXrg�resultrKrKrL�_to_relative_path�s

zIndexFile._to_relative_path�itemsrcCs�g}g}t|ttjf�r|g}|D]3}t|ttjf�r$|�|�|��qt|ttf�r4|�t�	|��qt|t�r?|�|�qt
d|��||fS)z?Split the items into two lists of path strings and BaseEntries.zInvalid Type: %r)�
isinstancer�rEr:r|r�rrr%r��	TypeError)rXr�r�rPr�rKrKrL�_preprocess_add_items�s
zIndexFile._preprocess_add_itemscs�t���}t|j�rdtf�fdd�}n	dtf�fdd�}|��!}|�d��|jj�tt	j
|j|��}|�d��Wd�n1sDwYtt
|j�|jdt��f�S)	z�Store file at filepath in the database and return the base index entry.

        :note:
            This needs the :func:`~git.index.util.git_working_dir` decorator active!
            This must be ensured in the calling code.
        r?csttt���td��S)N)�encoding)rr
rE�readlinkr	rK�r�rKrL�open_stream�sz*IndexFile._store_path.<locals>.open_streamcs
t�d�S�N�rb)r\rKr�rKrLr��s
FTNr)rEr�rr�r,rNr��storerr�type�st_sizer%r"r�r)rXr�r�r�r�r[�istreamrKr�rL�_store_path�s 

���zIndexFile._store_path�
path_rewriterrPcCs�g}|rK|D]?}t�|�r|}|tt|jj��dd�}n|}|jjr,t�|jj|�}t|jtjt	t
�|�j�t
|��}	|�t�|	��q|dd�=t|�dksSJ�|�|�D]}
|�|�|
|��qX|S)Nrr)r�r�r�r�rNr�r�r�NULL_BIN_SHAr"rE�statr�rr|r%r�r�r�)rXr�r�r�rP�
entries_addedrg�abspathZgitrelative_pathr�r�rKrKrL�_entries_for_paths�s*	
�
zIndexFile._entries_for_pathscG�dSrjrK�rrKrKrLro�r��forcerv�write_extension_datacs,|�|�\}�g}|r|�|�||�����r{dd��D�}	|	r%td��dd�t��D���r?td���fd	d
��}
|
|�|rYt��D]\}}t|j|j|j	||�f��|<qEt��D]\}}
|�v}|su�|
j
d|
��|
j
d|
�q]|���|D]
}
t�|
�|j
|
j
d
f<q}|r�|j|d�|S)aAdd files from the working tree, specific blobs, or
        :class:`~git.index.typ.BaseIndexEntry`\s to the index.

        :param items:
            Multiple types of items are supported, types can be mixed within one call.
            Different types imply a different handling. File paths may generally be
            relative or absolute.

            - path string

                Strings denote a relative or absolute path into the repository pointing
                to an existing file, e.g., ``CHANGES``, ``lib/myfile.ext``,
                ``/home/gitrepo/lib/myfile.ext``.

                Absolute paths must start with working tree directory of this index's
                repository to be considered valid. For example, if it was initialized
                with a non-normalized path, like ``/root/repo/../repo``, absolute paths
                to be added must start with ``/root/repo/../repo``.

                Paths provided like this must exist. When added, they will be written
                into the object database.

                PathStrings may contain globs, such as ``lib/__init__*``. Or they can be
                directories like ``lib``, which will add all the files within the
                directory and subdirectories.

                This equals a straight :manpage:`git-add(1)`.

                They are added at stage 0.

            - :class:`~git.objects.blob.Blob` or
              :class:`~git.objects.submodule.base.Submodule` object

                Blobs are added as they are assuming a valid mode is set.

                The file they refer to may or may not exist in the file system, but must
                be a path relative to our repository.

                If their sha is null (40*0), their path must exist in the file system
                relative to the git repository as an object will be created from the
                data at the path.

                The handling now very much equals the way string paths are processed,
                except that the mode you have set will be kept. This allows you to
                create symlinks by settings the mode respectively and writing the target
                of the symlink directly into the file. This equals a default Linux
                symlink which is not dereferenced automatically, except that it can be
                created on filesystems not supporting it as well.

                Please note that globs or directories are not allowed in
                :class:`~git.objects.blob.Blob` objects.

                They are added at stage 0.

            - :class:`~git.index.typ.BaseIndexEntry` or type

                Handling equals the one of :class:`~git.objects.blob.Blob` objects, but
                the stage may be explicitly set. Please note that Index Entries require
                binary sha's.

        :param force:
            **CURRENTLY INEFFECTIVE**
            If ``True``, otherwise ignored or excluded files will be added anyway. As
            opposed to the :manpage:`git-add(1)` command, we enable this flag by default
            as the API user usually wants the item to be added even though they might be
            excluded.

        :param fprogress:
            Function with signature ``f(path, done=False, item=item)`` called for each
            path to be added, one time once it is about to be added where ``done=False``
            and once after it was added where ``done=True``.

            ``item`` is set to the actual item we handle, either a path or a
            :class:`~git.index.typ.BaseIndexEntry`.

            Please note that the processed path is not guaranteed to be present in the
            index already as the index is currently being processed.

        :param path_rewriter:
            Function, with signature ``(string) func(BaseIndexEntry)``, returning a path
            for each passed entry which is the path to be actually recorded for the
            object created from :attr:`entry.path <git.index.typ.BaseIndexEntry.path>`.
            This allows you to write an index which is not identical to the layout of
            the actual files on your hard-disk. If not ``None`` and `items` contain
            plain paths, these paths will be converted to Entries beforehand and passed
            to the path_rewriter. Please note that ``entry.path`` is relative to the git
            repository.

        :param write:
            If ``True``, the index will be written once it was altered. Otherwise the
            changes only exist in memory and are not available to git commands.

        :param write_extension_data:
            If ``True``, extension data will be written back to the index. This can lead
            to issues in case it is containing the 'TREE' extension, which will cause
            the :manpage:`git-commit(1)` command to write an old tree, instead of a new
            one representing the now changed index.

            This doesn't matter if you use :meth:`IndexFile.commit`, which ignores the
            'TREE' extension altogether. You should set it to ``True`` if you intend to
            use :meth:`IndexFile.commit` exclusively while maintaining support for
            third-party extensions. Besides that, you can usually safely ignore the
            built-in extensions when using GitPython on repositories that are not
            handled manually at all.

            All current built-in extensions are listed here:
            https://git-scm.com/docs/index-format

        :return:
            List of :class:`~git.index.typ.BaseIndexEntry`\s representing the entries
            just actually added.

        :raise OSError:
            If a supplied path did not exist. Please note that
            :class:`~git.index.typ.BaseIndexEntry` objects that do not have a null sha
            will be added even if their paths do not exist.
        cSsg|]	}|jdkr|�qS)r)�moder�rKrKrLr��sz!IndexFile.add.<locals>.<listcomp>zXAt least one Entry has a null-mode - please use index.remove to remove files for claritycSs g|]\}}|jtjkr|�qSrK)r�rr�)r��irnrKrKrLr��s rXrr?Ncs@�D]}�|}|�|j��}t|j|j|j|jf��|<qdSrj)r�rgr%r�r�rl)rX�eiZ
null_entryZ	new_entry�rPr�Znull_entries_indicesrKrL�handle_null_entries�s�
��z*IndexFile.add.<locals>.handle_null_entriesFTr)rt)rXrr?N)r�r�r�r��	enumerater*r%r�r�rlrgr&r�rPrv)rXr�r�r�r�rvr�r�r�Znull_mode_entriesr�r�rnr�Z
progress_sentrKr�rL�add�s>� �
z
IndexFile.addcCszg}t|ttjf�r
|g}|D]+}t|tttff�r$|�|�|j	��qt|ttjf�r5|�|�|��qt
d|��|S)z}Returns a list of repo-relative paths from the given items which
        may be absolute or relative paths, entries or blobs.zInvalid item type: %r)r�r�rEr:r%rrr|r�rgr�)rXr�r�r�rKrKrL�_items_to_rela_paths�szIndexFile._items_to_rela_paths�working_treecKs\g}|s	|�d�|�d�tttj|�|���}|jjj||fi|���	�}dd�|D�S)a&Remove the given items from the index and optionally from the working tree
        as well.

        :param items:
            Multiple types of items are supported which may be be freely mixed.

            - path string

                Remove the given path at all stages. If it is a directory, you must
                specify the ``r=True`` keyword argument to remove all file entries below
                it. If absolute paths are given, they will be converted to a path
                relative to the git repository directory containing the working tree

                The path string may include globs, such as ``*.c``.

            - :class:`~git.objects.blob.Blob` object

                Only the path portion is used in this case.

            - :class:`~git.index.typ.BaseIndexEntry` or compatible type

                The only relevant information here is the path. The stage is ignored.

        :param working_tree:
            If ``True``, the entry will also be removed from the working tree,
            physically removing the respective file. This may fail if there are
            uncommitted changes in it.

        :param kwargs:
            Additional keyword arguments to be passed to :manpage:`git-rm(1)`, such as
            ``r`` to allow recursive removal.

        :return:
            List(path_string, ...) list of repository relative paths that have been
            removed effectively.

            This is interesting to know in case you have provided a directory or globs.
            Paths are relative to the repository.
        z--cachedz--cSsg|]}|dd��qS)����rK)r��prKrKrLr�r�z$IndexFile.remove.<locals>.<listcomp>)
r|�list�maprEr�rrNr}Zrm�
splitlines)rXr�rr�rr�Z
removed_pathsrKrKrLrG�s/

zIndexFile.remove�skip_errorscKsg}|r	|�d�|�|�}t|�dkrtd��|�d|�dd��}d|d<g}|jjj||fi|����}t	t
t|�d�t|��D]&}	||	�d�}
t|
�dksZJd	||	��|�|
d
dd�|
df�qC|rn|S|�d�|jjj||fi|��|S)
a�Rename/move the items, whereas the last item is considered the destination of
        the move operation.

        If the destination is a file, the first item (of two) must be a file as well.

        If the destination is a directory, it may be preceded by one or more directories
        or files.

        The working tree will be affected in non-bare repositories.

        :param items:
            Multiple types of items are supported, please see the :meth:`remove` method
            for reference.

        :param skip_errors:
            If ``True``, errors such as ones resulting from missing source files will be
            skipped.

        :param kwargs:
            Additional arguments you would like to pass to :manpage:`git-mv(1)`, such as
            ``dry_run`` or ``force``.

        :return:
            List(tuple(source_path_string, destination_path_string), ...)

            A list of pairs, containing the source file moved as well as its actual
            destination. Relative to the repository root.

        :raise ValueError:
            If only one item was given.

        :raise git.exc.GitCommandError:
            If git could not handle your request.
        z-krSzLPlease provide at least one source and one destination of the move operation�dry_run�nNTz to zToo many tokens in %sr�	r)r|rr�r�r�rNr}�mvr�range�int�split)rXr�r	r�rr�Zwas_dry_run�outZmvlinesZln�tokensrKrKrL�moves&*

 
zIndexFile.move�message�parent_commits�head�author�	committer�author_date�commit_date�
skip_hooks�trailers)NzDict[str, str]zList[Tuple[str, str]]c
Csr|std|�|�|�td||���|��}|��|��}
tj|j|
||||||||	d�
}|s7td|�|S)a�Commit the current default index file, creating a
        :class:`~git.objects.commit.Commit` object.

        For more information on the arguments, see
        :meth:`Commit.create_from_tree <git.objects.commit.Commit.create_from_tree>`.

        :note:
            If you have manually altered the :attr:`entries` member of this instance,
            don't forget to :meth:`write` your changes to disk beforehand.

        :note:
            Passing ``skip_hooks=True`` is the equivalent of using ``-n`` or
            ``--no-verify`` on the command line.

        :return:
            :class:`~git.objects.commit.Commit` object representing the new commit
        z
pre-commitz
commit-msg)rrrrrzpost-commit)	r!�_write_commit_editmsg�_commit_editmsg_filepath�_read_commit_editmsg�_remove_commit_editmsgr�rZcreate_from_treerN)rXrrrrrrrrrZtreer�rKrKrLrxfs,

�
zIndexFile.commitcCsDt|��d��}|�|�t��Wd�dS1swYdS)N�wb)r\rrvr�r	)rXr�commit_editmsg_filerKrKrLr�s"�zIndexFile._write_commit_editmsgcCst�|���dSrj)rErGrrfrKrKrLr �sz IndexFile._remove_commit_editmsgcCs@t|��d��}|���t�Wd�S1swYdSr�)r\r�read�decoder	)rXr"rKrKrLr�s$�zIndexFile._read_commit_editmsgcCst�|jjd�S)NZCOMMIT_EDITMSG)r�r�rNZ
common_dirrfrKrKrLr�sz"IndexFile._commit_editmsg_filepath�Popen[bytes]�
ignore_stdoutcCsN|j}|r
|��|��d}|s|jr|j��}|jr%|j��|��|S)NrU)r�r�rFr�r#�wait)r�r�r&Zstdin_IOr�rKrKrL�_flush_stdin_and_wait�s


zIndexFile._flush_stdin_and_waitcGr�rjrKr�rKrKrLro�r�c
sdg�|r
��d�g�g�g�dddttddf���fdd	�}|durY��d
�d|d<|dd
d�|jjj�i|������|ddd�dd�|j��D�}|�|�|St	|t
�ra|g}|j��d�d|d<tj|d<|jjj�fi|���dt
f��fdd�}g}|D]a}	t|�|	��}
d
}z	|j|
dfWn:ty�|
}|�d�s�|d7}|j��D] }
t�|
j��|�r�|
j}|j�||||d
d�|�|�d}q�Ynw|s�|j�|
|	||d
d�|�|
�q�z	|j�dd�Wnt
�ytd�g���w|�|�|S)a�Check out the given paths or all files from the version known to the index
        into the working tree.

        :note:
            Be sure you have written pending changes using the :meth:`write` method in
            case you have altered the entries dictionary directly.

        :param paths:
            If ``None``, all paths in the index will be checked out.
            Otherwise an iterable of relative or absolute paths or a single path
            pointing to files or directories in the index is expected.

        :param force:
            If ``True``, existing files will be overwritten even if they contain local
            modifications.
            If ``False``, these will trigger a :exc:`~git.exc.CheckoutError`.

        :param fprogress:
            See :meth:`IndexFile.add` for signature and explanation.

            The provided progress information will contain ``None`` as path and item if
            no explicit paths are given. Otherwise progress information will be send
            prior and after a file has been checked out.

        :param kwargs:
            Additional arguments to be passed to :manpage:`git-checkout-index(1)`.

        :return:
            Iterable yielding paths to files which have been checked out and are
            guaranteed to match the version stored in the index.

        :raise git.exc.CheckoutError:
            * If at least one file failed to be checked out. This is a summary, hence it
              will checkout as many files as it can anyway.
            * If one of files or directories do not exist in the index (as opposed to
              the original git command, which ignores them).

        :raise git.exc.GitCommandError:
            If error lines could not be parsed - this truly is an exceptional state.

        :note:
            The checkout is limited to checking out the files in the index. Files which
            are not in the index anymore and exist in the working tree will not be
            deleted. This behaviour is fundamentally different to ``head.checkout``,
            i.e. if you want :manpage:`git-checkout(1)`-like behaviour, use
            ``head.checkout`` instead of ``index.checkout``.
        z--indexz--forcer�r%�iter_checked_out_filesr?Ncs`|j}|sdS|��}|�t�}d}|��D]|}|�d�su|�d�sud}d}d}	|�|�r?��|dt|�����|�n5|�|�rX��|t|�|�	d�����|�n|�|	�ro��|dt|	�����|	�n��|�q|D]}
|�|
�r���|dt|
�����|
�nqwq�r�t
d	d
|���r�tt|�t���}t
d�|���dS)N)z already existsz is not in the cachez does not exist at stagez is unmergedzgit checkout-index: zgit-checkout-index: z is a directoryzunable to unlink old 'z already exists, no checkout�'�)�git-checkout-index�zMSome files could not be checked out from the index due to local modifications)�stderrr#r$r	rr�r�r|r��rfindrr�setr)r�r)Z	stderr_IOZstderr_bytesr.Zendingsr�Zis_a_dirZunlink_issueZalready_exists_issuernZvalid_files)�failed_files�failed_reasons�
unknown_linesrKrL�
handle_stderr�sP






����z)IndexFile.checkout.<locals>.handle_stderrz--allrZ
as_processFTcss�|]}|jVqdSrjr�r�rKrKrLr�5s�z%IndexFile.checkout.<locals>.<genexpr>z--stdinr�cstdg��Rd�j���S)Nr,r-)rr.r#rK)rr�rKrL�make_excGsz$IndexFile.checkout.<locals>.make_excr�/)r�)r&zWSome files could not be checked out from the index, probably because they didn't exist.)r|r1r:rNr}Zcheckout_indexr'rPrrr�r��
subprocess�PIPErrr�r�r�rEr�rgr�r�r(r)rXr�r�r�r�r4Z	rval_iterr5Zchecked_out_filesrgZco_pathZpath_is_directoryZfolderr�rrK)rr1r2r�r3rL�checkout�sx7
"7






���
���
	zIndexFile.checkout�HEADrxr<c
Ks�t|��|j|�}|s|j|_n4|j}|D].}|�|�}zt|d�}	||	|j|	<WqtyCz|j|	=Wn	ty@YnwYqw|��|rQ|j|dd�|rb|jj	j
|j�|�d|d�|S)a[Reset the index to reflect the tree at the given commit. This will not adjust
        our HEAD reference by default, as opposed to
        :meth:`HEAD.reset <git.refs.head.HEAD.reset>`.

        :param commit:
            Revision, :class:`~git.refs.reference.Reference` or
            :class:`~git.objects.commit.Commit` specifying the commit we should
            represent.

            If you want to specify a tree only, use :meth:`IndexFile.from_tree` and
            overwrite the default index.

        :param working_tree:
            If ``True``, the files in the working tree will reflect the changed index.
            If ``False``, the working tree will not be touched.
            Please note that changes to the working copy will be discarded without
            warning!

        :param head:
            If ``True``, the head will be set to the given commit. This is ``False`` by
            default, but if ``True``, this method behaves like
            :meth:`HEAD.reset <git.refs.head.HEAD.reset>`.

        :param paths:
            If given as an iterable of absolute or repository-relative paths, only these
            will be reset to their state at the given commit-ish.
            The paths need to exist at the commit, otherwise an exception will be
            raised.

        :param kwargs:
            Additional keyword arguments passed to :manpage:`git-reset(1)`.

        :note:
            :meth:`IndexFile.reset`, as opposed to
            :meth:`HEAD.reset <git.refs.head.HEAD.reset>`, will not delete any files in
            order to maintain a consistent working tree. Instead, it will just check out
            the files according to their state in the index.
            If you want :manpage:`git-reset(1)`-like behaviour, use
            :meth:`HEAD.reset <git.refs.head.HEAD.reset>` instead.

        :return:
            self
        rT)r�r�z%s: Updating HEAD)Zlogmsg)r�r�rNrPr�rr�rvr9rZ
set_commitrx)
rXrxrr�rr�Znew_instZniergrprKrKrL�resetus.6


���
zIndexFile.reset�otherrr�create_patchcs�|j|��krtd|����||jurt��St|t�r#|j	�
|�}t|t�r?|�dd�}||d<|j|j||fi|��S|durIt
d|��t�j|||fi|��S)a�Diff this index against the working copy or a :class:`~git.objects.tree.Tree`
        or :class:`~git.objects.commit.Commit` object.

        For documentation of the parameters and return values, see
        :meth:`Diffable.diff <git.diff.Diffable.diff>`.

        :note:
            Will only work with indices that represent the default git index as they
            have not been initialized with a stream.
        zECannot call %r on indices that do not represent the default git index�RFNz<other must be None, Diffable.INDEX, a Tree or Commit, was %r)rRrW�AssertionError�diff�INDEX�git_diff�	DiffIndexr�r�rNZ	rev_parser�getr�r`)rXr<r�r=r�Zcur_valrbrKrLr@�s



zIndexFile.diffrj)r?N)F)NF)T)r?r)NTNNNNFN)r:FNF)S�__name__�
__module__�__qualname__�__doc__�	__slots__rVrr8r:rYr�rarW�propertyrgrir0r_r3r&rsr�rurvr(r)�Treeishr��classmethodrr�r+r�rr5r2r�r-rr�r7rrr�r.r�r%rr�r�r�r�r�r�r�r*r�rrrrGrrr�datetimerxrr rr�bytesr(r1r9r;rBrAr9Z
DiffConstantsrCZDiffr@�
__classcell__rKrKrbrLrns� 

�
��
�($# E B����
���

�1��
�"&
' �
��
� �
����*�������
�M�
������:�����Q����
�
���	�
�
�5
������=�������_�
���	�
��
�r)`rH�__all__�
contextlibrMr��iorrEZos.pathrgr�r�rr7rBrDZ
gitdb.baserZgitdb.dbrZ
git.compatr	r
Zgit.diffr@rBZgit.excrrrr
Zgit.objectsrrrrrZgit.objects.utilrZgit.utilrrrrrrrrZfunrrrr r!r"r#r$�typr%r&r�utilr'r(r)r*�typingr+r,r-r.r/r0r1r2r3r4r5r6r7r8Z	git.typesr9r:r;Zgit.refs.referencer<Zgit.repor=r�rNrK�contextmanagerrMZDiffablerrKrKrKrL�<module>sB((
@
@ Telegram