U 楡c{@s~dZddlmZmZmZddlmZddlmZm Z m Z ddl m Z ddl mZddlZddlZdZGd d d eeeeZdS) z/Module containing a database to deal with packs) FileDBBase ObjectDBR CachingDB) LazyMixin) BadObjectUnsupportedOperationAmbiguousObjectName) PackEntity)reduceN)PackedDBcseZdZdZdZfddZddZddZd d Zd d Z d dZ ddZ ddZ ddZ ddZdddZddZddZZS)r z-A database operating on a set of object packsicst|d|_d|_dSNr)super__init__ _hit_count _st_mtime)self root_path __class__1/tmp/pip-unpacked-wheel-jjg5dubb/gitdb/db/pack.pyr)s zPackedDB.__init__cCs |dkrt|_|jdddS)N _entitiesT)force)listr update_cache)rattrrrr _set_cache_3szPackedDB._set_cache_cCs|jjdddddS)NcSs|dSr r)lrrr:z)PackedDB._sort_entities..T)keyreverse)rsortrrrr_sort_entities9szPackedDB._sort_entitiescCsr|j|jdkr||jD]F}|d|}|dk r|dd7<|jd7_|d|fSqt|dS)a:return: tuple(entity, index) for an item at the given sha :param sha: 20 or 40 byte sha :raise BadObject: **Note:** This method is not thread-safe, but may be hit in multi-threaded operation. The worst thing that can happen though is a counter that was not incremented, or the list being in wrong order. So we safe the time for locking here, lets see how that goesrN)r_sort_intervalr$rr)rshaitemindexrrr _pack_info<s   zPackedDB._pack_infocCs,z||WdStk r&YdSXdS)NTF)r+r)rr(rrr has_objectYs  zPackedDB.has_objectcCs||\}}||SN)r+Z info_at_indexrr(entityr*rrrinfoasz PackedDB.infocCs||\}}||Sr-)r+Zstream_at_indexr.rrrstreameszPackedDB.streamccs<|D].}|}|j}t|D]}||Vq&qdSr-)entitiesr*r(rangesize)rr/r*Z sha_by_indexrrrsha_iteris  zPackedDB.sha_itercCs dd|jD}tdd|dS)NcSsg|]}|dqSr&)r*r4.0r)rrr ssz!PackedDB.size..cSs||Sr-r)xyrrrrtrzPackedDB.size..r)rr )rZsizesrrrr4rsz PackedDB.sizecCs tdS)zStoring individual objects is not feasible as a pack is designed to hold multiple objects. Writing or rewriting packs for single objects is inefficientN)r)rZistreamrrrstorezszPackedDB.storeFc Cst|}|s"|j|jkr"dS|j|_tttj|d}dd|j D}||D],}t |}|j | ||jgq^||D]L}d}t|j D]$\}} | d |kr|}qq|dkst|j |=q|dS)a Update our cache with the actually existing packs on disk. Add new ones, and remove deleted ones. We keep the unchanged ones :param force: If True, the cache will be updated even though the directory does not appear to have changed according to its modification timestamp. :return: True if the packs have been updated so there is new information, False if there was no change to the pack databaseFz pack-*.packcSsh|]}|dqSr6)packpathr7rrr sz(PackedDB.update_cache..r&T)osstatrst_mtimersetglobr>joinrr appendr=r4r*Z sha_to_index enumerateAssertionErrorr$) rrrBZ pack_filesZour_pack_filesZ pack_filer/Z del_indexir)rrrrs&  "   zPackedDB.update_cachecCsdd|jDS)z=:return: list of pack entities operated upon by this databasecSsg|] }|dqSr6rr7rrrr9sz%PackedDB.entities..)rr#rrrr2szPackedDB.entitiescCsjd}|jD]J}|d||}|dk r |d|}|rP||krPt||}q |r^|St|dS)a:return: 20 byte sha as inferred by the given partial binary sha :param partial_binsha: binary sha with less than 20 bytes :param canonical_length: length of the corresponding canonical representation. It is required as binary sha's cannot display whether the original hex sha had an odd or even number of characters :raise AmbiguousObjectName: :raise BadObject: Nr&)rr*Zpartial_sha_to_indexr(rr)rZpartial_binshaZcanonical_length candidater)Z item_indexr(rrrpartial_to_complete_shas  z PackedDB.partial_to_complete_sha)F)__name__ __module__ __qualname____doc__r'rrr$r+r,r0r1r5r4r<rr2rL __classcell__rrrrr s   -r )rPZ gitdb.db.baserrrZ gitdb.utilrZ gitdb.excrrrZ gitdb.packr functoolsr rArE__all__r rrrrs