Result for 19C18FC79AD843CA7B56D69CE6FEA46D7F819F85

Query result

Key Value
FileName./usr/lib/python3.8/site-packages/dogpile/cache/backends/__pycache__/memcached.cpython-38.pyc
FileSize12999
MD59CF210C848BFAE0BCC8612B0B12E0741
SHA-119C18FC79AD843CA7B56D69CE6FEA46D7F819F85
SHA-256D8B839457552F81DE00D2A9427B9EF87FB1A773D36CF6ED5CCFFE0D16DE26A58
SSDEEP192:aKRJfrbd8kdfblwpb3h6W9xX7/RHuQPg2tMZUMC2VU0jD4bLd/K5F:dJfHd8gfb6pL4M7/NuQVMs5Ld/gF
TLSHT10142858E4E4648B2FEE2F6BA74794230533A832BB7855122F45CD19D0F4D588CFBD698
hashlookup:parent-total1
hashlookup:trust55

Network graph view

Parents (Total: 1)

The searched file hash is included in 1 parent files which include package known and seen by metalookup. A sample is included below:

Key Value
MD51FA37725D5DFFC63B875EE18916D693F
PackageArchnoarch
PackageDescriptionDogpile consists of two subsystems, one building on top of the other. dogpile provides the concept of a "dogpile lock", a control structure which allows a single thread of execution to be selected as the "creator" of some resource, while allowing other threads of execution to refer to the previous version of this resource as the creation proceeds; if there is no previous version, then those threads block until the object is available. dogpile.cache is a caching API which provides a generic interface to caching backends of any variety, and additionally provides API hooks which integrate these cache backends with the locking mechanism of dogpile. Overall, dogpile.cache is intended as a replacement to the Beaker caching system, the internals of which are written by the same author. All the ideas of Beaker which "work" are re- implemented in dogpile.cache in a more efficient and succinct manner, and all the cruft (Beaker's internals were first written in 2005) relegated to the trash heap.
PackageMaintainerjoequant <joequant>
PackageNamepython3-dogpile-cache
PackageRelease1.mga8
PackageVersion1.0.2
SHA-131F2A14FE99DFD8DBB3564737267A26D675E2501
SHA-25606A2F8C27846199D6870D77EB4718CE569C457C7F3D24D200AD68962C8E0B12F