.Ph4 dZddlZddlZddlmZddlmZmZmZm Z m Z m Z ddl m Z mZmZmZmZmZddlmZddlmZ dd ed eed ed ed eeeff dZde eefd efdZded efdZde eefd efdZd eded eed efdZd eded efdZd ed eeded e efdZd ed efdZ d ed efdZ!d ed efdZ"ded efdZ#dS)aWCompute the content hash of a lock specification. The content hash is used with `conda-lock --check-content-hash` to avoid unnecessary relocking when the lock specification is unchanged. Note that the content hash depends not only on the LockSpecification object but also the virtual package specification. WARNING: The fundamental concept of a content hash is seriously flawed: It is important to maintain the content hash for backwards compatibility, but we should stop using it in the future. Note that anything that modifies the content hash is a breaking change, since it will invalidate all existing lockspecs. The content hash is computed by JSON-serializing the lock specification and the virtual package specification, and then hashing the serialized representation. Ndeepcopy)DictOptionalSequenceSetUnioncast) EmptyDict$HashableVirtualPackageRepresentationPlatformSubdirStrSerializedDependencySerializedLockspecSubdirMetadata)LockSpecification) FakeRepoDataT lock_specvirtual_package_reporeinsert_spurious_build_numberremove_new_nullsreturnci}|r|t|}|jD]6}t|||}|rt|}t |||<7|S)aCompute the content hashes for the given lock specification. Args: lock_spec: The lock specification to compute the content hashes for. virtual_package_repo: The virtual package repository to use. If None, the content hash is computed without the VPR. reinsert_spurious_build_number: Whether to reinsert the spurious build number in the build string of the VPR. This prevents the content hash from changing when upgrading from v2 to v3.0.3. remove_new_nulls: Whether to remove newly added fields from the package specs when they are null. This prevents the content hash from changing when upgrading from v2 to v3.0.3. Returns: A dictionary of platform-specific content hashes. )_reinsert_spurious_build_number platforms_content_for_platform_remove_new_nulls _dict_to_hash)rrrrresultplatformcontents W/var/www/html/test/jupyter/venv/lib/python3.11/site-packages/conda_lock/content_hash.pycompute_content_hashesr")s|2,.F&U*>*J>?STT'22' 8=QRR  1'00G(11x Mdc.tj|dS)z:Produce a canonical JSON representation of the given dict.T) sort_keys)jsondumpsr$s r! _dict_to_jsonr*Qs :a4 ( ( ((r#scttj|dS)zHash the given JSON string.zutf-8)hashlibsha256encode hexdigest)r+s r! _json_to_hashr1Xs* >!((7++ , , 6 6 8 88r#c:tt|S)zHash the given dict.)r1r*r)s r!rr]s q)) * **r#rcd|jDdt|j|dDd}|jrd|jD|d<|t |||d<|S) Nc6g|]}|Smodel_dump_json).0cs r! z)_content_for_platform..js$EEEQQ&&((EEEr#c\g|])}tt|*Sr5)r r model_dump)r8ps r!r:z)_content_for_platform..ks;    %q||~~ 6 6   r#c|j|jfS)N)managername)r=s r!z'_content_for_platform..nsAF@Sr#)key)channelsspecsc6g|]}|Sr5r6)r8repos r!r:z)_content_for_platform..ss13 3 3 '+D " "3 3 3 r#pip_repositoriesvirtual_package_hash)rCsorted dependenciesrG%_virtual_package_content_for_platform)rrrserialized_lockspecs r!rrds FE)2DEEE  &x06S6S   //! 3 3 /8/I3 3 3 ./' 12F Q Q 23 r#c|j}ddiid}d|iid}i}i}d|d|||||i}|S)zSerialize the virtual package content into a dict for hashing. This is used in the computation of the content hash, and goes into the "virtual_package_hash" field of the serialized lockspec. subdirnoarch)infopackages) all_repodataget)rrvpr_datafallback_noarchfallback_platformrs r!rKrK}s$0H 8$99O 8$;;O (,,x99(,,x):;;4F Mr#c \g}||g}|D]9}|dkr1t|r"|t|:|D]$}|t |%|t |dksJdg}nt |dksJ|}t }|D]Z}|t||dd||t||dd|[|S)aCompute a set of content hashes for equivalent lock specifications. Computing multiple content hashes allows us to support previous versions of the content hash computation for backwards compatibility. We could have adopted a more targeted strategy for producing specific variants of the VPR, but the VPR can also be customized, so it's hard to know exactly how it's constructed. Therefore we just enumerate all possible variants to be safe. Note that VPR=None is only used for old tests, and it corresponds to the case where VPR is unspecified rather than default. (TODO: replace those tests and eliminate this special case?) Nosx-64rF)rrrrT) copy_contains_osx_11_0_0_tar_bz2append!add_or_remove_osx_10_15_0_tar_bz2rlensetaddr")rrrvirtual_package_repo_variantsvprvprsallowed_hashes vpr_or_nones r!#backwards_compatible_content_hashesres$9;!' *>(>%-1133YY x  $@$E$E  ) 0 01RSV1W1W X X X-1133SS%,,-LS-Q-QRRRR#011Q6666v011A5555, #uuN   "#%0/4!&            "#%0/4!%            r#c |d}tt|jd}|d}d|vr|d=ndddd dgd d d dd |d<|S)aCAdd or remove the __osx 10.15 virtual package. Adds __osx 10.15 if it is not present, and removes it if it is present. This way, whichever convention we start with, the opposite convention will be produced. Rationale: In 6f69901 we started generating the default repodata based on default-virtual-packages.yaml instead of programmatically. But there was a bug in which we added both __osx 10.15 and 11.0. The extra 10.15 is ignored by conda and mamba, and 11.0 takes precedence. We added an option to readd the 10.15 package in 777dfbf. TdeeprXrQz__osx-10.15-0.tar.bz2__osxz10.15r>virtual_system0 r@version build_string build_numberrOdepends timestamp package_typebuildrN) model_copyr rrR)rrrdrQs r!r\r\s " , ,$ , 7 7Fnf.A(.KLLB*~H(** , - -&, - - () Mr#c |jdi}d|vrdStt|}|dddddddgd d d dd kS) NrXrQFz__osx-11.0-0.tar.bz2riz11.0rjrrkrlrmrn)rRrSr r)rrws r!rZrZs  * . .x <  4 5 5"( : :  r#c |d}|jD]}|j|}d|vrtt|}|dD]d\}}|d}|d}|d}|d} t |dkr,|d | |d <|d |d |d | d } ||d| <|d|=e|S) aReinsert the spurious build number in the build string. This was introduced in v3.0.3 to reproduce the content hash of the v2 lockfiles. Without the spurious build number: ```json "__archspec-1-x86_64.tar.bz2": { "build": "x86_64", "build_number": 0, "build_string": "x86_64", "depends": [], "name": "__archspec", "noarch": "", "package_type": "virtual_system", "subdir": "linux-64", "timestamp": 1577854800000, "version": "1" } ``` With the spurious build number: ```json "__archspec-1-x86_64_0.tar.bz2": { "build": "x86_64_0", "build_number": 0, "build_string": "x86_64", "depends": [], "name": "__archspec", "noarch": "", "package_type": "virtual_system", "subdir": "linux-64", "timestamp": 1577854800000, "version": "1" } ``` TrgrQr@rorprqr_ru-z.tar.bz2)rvrRr rrYitemsr]) rrrrw package_name package_datar@rorprqnew_names r!rr#sN" , ,$ , 7 7F' 5 5   *   nb))B.0n.A.A.C.C.I.I.K.K 5 5* l#F+&y1+N; +N; |$$q((/;,L,Ll,L,LL)"&XXXX<XX,XXXH/;BzN8,:|4 Mr#r cvt|}|dD] }d|vr |d|d=d|vr |d|d=!|S)zRemove newly added fields from the VPR when they are null. New fields added in v3.0.0 that are usually None but were absent in v2 would alter the content hash, so we remove them for backwards compatibility. rDmarkersN subdirectoryr)r rspecs r!rr\sb g  Fw%%   i!8Y T ! !d>&:&B^$ Mr#)TT)$__doc__r-r'rYrtypingrrrrr r conda_lock.content_hash_typesr r r rrrconda_lock.models.lock_specrconda_lock.virtual_packagerboolstrr"r*r1rrrKrer\rZrrr5r#r!rs , ================:99999333333 ,0! %% %"<0%%)% %  S ! %%%%P) !E EF)))))9S9S9999 + !E EF+++++ #<0 2!&!!*!!!!HD D"<0D D X DDDDN%&%%%%%P|&6,6<6666r 1 6H      r#