(6 FddlZddlmZddlmZmZej dZdZdZ ejdZ ejdZ ee jk(sJe e jk(sJd Zd Zd Zd Zej$Gd dZdZdZdZdZdZy)N)attr)errorpolicyparsers,z >LLLLL4s20sz>LHHLHLLLLHllli c\tj|\}}}}}} } t|||||y)a:parse a full v2-dirstate from a binary data into dictionaries: - map: a {path: entry} mapping that will be filled - copy_map: a {path: copy-source} mapping that will be filled - data: a binary blob contains v2 nodes data - tree_metadata:: a binary blob of the top level node (from the docket) N) TREE_METADATAunpack parse_nodes) mapcopy_mapdata tree_metadataroot_nodes_startroot_nodes_len_nodes_with_entry_count_nodes_with_copy_source_count_unreachable_bytes_unused_ignore_patterns_hashs >usr/lib/python3.12/site-packages/mercurial/dirstateutils/v2.pyparse_dirstater>s= ]+%Xt%5~Fcjt|D]}|t|zz}t||t}tj |\ }} } } } } }}}}}}}t |||| |t jj||||}|jst||| }|||<| st|| | ||<y)aparse nodes from starting at offset This is used by parse_dirstate to recursively fill `map` and `copy_map`. All directory specific information is ignored and do not need any processing (DIRECTORY, ALL_UNKNOWN_RECORDED, ALL_IGNORED_RECORDED) N) range NODE_SIZEslice_with_lenNODEr r r DirstateItem from_v2_data any_tracked)r rrstartleni node_start node_bytes path_startpath_len_basename_startcopy_source_startcopy_source_lenchildren_startchildren_count_descendants_with_entry_count_tracked_descendants_countflagssizemtime_smtime_nsitempaths rr r Rs3ZY]* #D*i@  KK #        ) &     C4H##00gxP dJ9D +'HTN9rc||||zSN)rr#r$s rrr{s  $$rceZdZejZejZejdZejdZejdZ ejdZ ejdZ dZ y)NodeN)defaultrc|j}|j|}|j}|}t|}|j ddz}||t|z} t|} nd} d} ||j \} } } }n t } d} d} d}tj|||| | |j|j|j|j| | | | S)N/r) r6getentryr$rfindv2_dataDIRSTATE_V2_DIRECTORYrpackchildren_offsetr.descendants_with_entrytracked_descendants)selfr paths_offsetr6copyrAr(r)basename_startr+r,r1r2r3r4s rrEz Node.packsyy||D! ! t9D)A-   ,s4y 8 !$iO ! O  -2]]_ *E4(*EDGHyy           ' '  $ $      r) __name__ __module__ __qualname__ribr6rAparentr.rFrGrHrEr9rrr;r;ss 4779D DGGIE TWWT "FTWWQ'Ndgga(O$TWWQ/!$''!,$ rr;c t}d}d}d}d}d}d}d} t|dk(rtj||||||| } || fSt |j d} g} t dd} | j| t| dD]?\}\}}|dz }||vr|dz }t|}t|| | } | xjdz c_ |jr| xjdz c_ | xjdz c_| jt ||| d }d}|t| kr| |d}t|| }|st!| ||| | s| j"dk7s| j$}|duxr"t|t| d j"}||rt!|||| |} | s0| j"dk7r^B| j'} | j"dk(sJ| j"t| dk(sJt| tj| j(| j||||| } || fS) a5 Pack `map` and `copy_map` into the dirstate v2 binary format and return the tuple of (data, metadata) bytearrays. The on-disk format expects a tree-like structure where the leaves are written first (and sorted per-directory), going up levels until the root node and writing that one to the docket. See more details on the on-disk format in `mercurial/helptext/internals/dirstate-v2`. Since both `map` and `copy_map` are flat dicts we need to figure out the hierarchy. This algorithm does so without having to build the entire tree in-memory: it only keeps the minimum number of nodes around to satisfy the format. # Algorithm explanation This explanation does not talk about the different counters for tracked descendants and storing the copies, but that work is pretty simple once this algorithm is in place. ## Building a subtree First, sort `map`: this makes it so the leaves of the tree are contiguous per directory (i.e. a/b/c and a/b/d will be next to each other in the list), and enables us to use the ordering of folders to have a "cursor" of the current folder we're in without ever going twice in the same branch of the tree. The cursor is a node that remembers its parent and any information relevant to the format (see the `Node` class), building the relevant part of the tree lazily. Then, for each file in `map`, move the cursor into the tree to the corresponding folder of the file: for example, if the very first file is "a/b/c", we start from `Node[""]`, create `Node["a"]` which points to its parent `Node[""]`, then create `Node["a/b"]`, which points to its parent `Node["a"]`. These nodes are kept around in a stack. If the next file in `map` is in the same subtree ("a/b/d" or "a/b/e/f"), we add it to the stack and keep looping with the same logic of creating the tree nodes as needed. If however the next file in `map` is *not* in the same subtree ("a/other", if we're still in the "a/b" folder), then we know that the subtree we're in is complete. ## Writing the subtree We have the entire subtree in the stack, so we start writing it to disk folder by folder. The way we write a folder is to pop the stack into a list until the folder changes, revert this list of direct children (to satisfy the format requirement that children be sorted). This process repeats until we hit the "other" subtree. An example: a dir1/b dir1/c dir2/dir3/d dir2/dir3/e dir2/f Would have us: - add to the stack until "dir2/dir3/e" - realize that "dir2/f" is in a different subtree - pop "dir2/dir3/e", "dir2/dir3/d", reverse them so they're sorted and pack them since the next entry is "dir2/dir3" - go back up to "dir2" - add "dir2/f" to the stack - realize we're done with the map - pop "dir2/f", "dir2/dir3" from the stack, reverse and pack them - go up to the root node, do the same to write "a", "dir1" and "dir2" in that order ## Special case for the root node The root node is not serialized in the format, but its information is written to the docket. Again, see more details on the on-disk format in `mercurial/helptext/internals/dirstate-v2`. rssc*|djdS)Nrr>)split)xs rzpack_dirstate..s1Q4::d3Cr)keyrNr?T) bytearrayr$r rEsorteditemsr;append enumerate get_foldermove_to_correct_node_in_treer.trackedrHrG is_ancestorpack_directory_childrenr6rQpoprF)r rrrrnodes_with_entry_countnodes_with_copy_source_countunreachable_bytesunusedignore_patterns_hashr sorted_mapstack current_nodeindexr6rAcurrent_folder should_pack next_pathrQin_ancestor_of_next_paths r pack_dirstaterqsV ;DN#$  F' 3x1}%**   " (    ]"" )CDJ ET?L LL )*a 8}e!# 8  (A - (#D)3 L%  ##q(# ==  , , 1 ,++q0+ T$|45  3z? "#5)!,I))^DDK  #L(D% HL--4&,,+4D+@, :eBinn+EF)>%='$F% L--43!9N99;L    #6\%6%66 # u:?&CJ&?!&&$$##$M  rc8d|vr|jdddSdS)zU Return the folder of the path that's given, an empty string for root paths. r>r?rr)rsplit)r6s rr^r^Ss%'+dl4;;tQ  ";;rc|dk(ry||kry|jd}|jd}tdt||DS)aReturns whether `maybe_ancestor` is an ancestor of `path`. >>> is_ancestor(b"a", b"") True >>> is_ancestor(b"a/b/c", b"a/b/c") False >>> is_ancestor(b"hgext3rd/__init__.py", b"hgext") False >>> is_ancestor(b"hgext3rd/__init__.py", b"hgext3rd") True rTFr>c3,K|] \}}||k(ywr8r9).0cos r zis_ancestor..lsL"K$!QqAv"Ks)rTallzip)r6maybe_ancestorpath_componentsancestor_componentss rraraZsR ~jj&O(..t4 L#o7J"KL LLrc||jk7rt||jr|t|jdjd}|j ddd}|jr|jdz|z}n|}|d}|j|k(r|}n@|xj dz c_t |d|}|j|n |j}||jk7r|S)z Move inside the dirstate node tree to the node corresponding to `target_folder`, creating the missing nodes along the way if needed. Nr>r?rrX) r6rar$lstriprTr.r;r\rQ) target_folderrkrjprefixsubfolder_namesubfolder_path next_nodes rr_r_os <,, , }l&7&7 8"3|'8'8#9#;<CCDIF#\\$215N  !-!2!2T!9N!J!/b I~~. ) ++q0+#ND,G  \*(..L) <,, ,* rcRg}|djdk7r|t|dj|jk(rW|j|j|djdk7r&t|dj|jk(rW|s"t j d|jz|j t}|D]}|j|t|}|j||j|j|j|j|jd|xj|jz c_ |xj|jz c_ t||_|j|y)z_ Write the binary representation of the direct sorted children of `node` to `data` rXrsno direct children for %r)rrJN)r6r^r\rcrProgrammingErrorreverserYrEr$extendr@rHrGrF)noderrrjdirect_childrenpacked_childrenchildpackeds rrbrbsC O )..C JuRy~~$>$))$Kuyy{+ )..C JuRy~~$>$))$K $$%ADII%MNNkO XCIFv& EJJ HLLS12   E$=$==  ##u'C'CC# !t9DKK r)struct thirdpartyrrr importmodrTREE_METADATA_SIZErStructr rr2rDrr rsr;rqr^rar_rbr9rrrs &  9 %    m, &v}}%&]/////DII G(&R%- - - ``F<M*:!r