Result for 05189E0C0C33795996A1E39958124B3586F2970C

Query result

Key Value
FileName./usr/share/gocode/src/sigs.k8s.io/structured-merge-diff/schema/equals_test.go
FileSize3663
MD50A654BC5DC345C314331567F27C44BAC
SHA-105189E0C0C33795996A1E39958124B3586F2970C
SHA-256577175FE69FF2C254420CE156F3982BEBD149912F7BF849D39CADCFF7D710D0E
SSDEEP96:K+4s3HFK5kzAxk/skG/kK51F3RCJs16JIlDP/ps16SPt:j33HZzf7fc0s162Zs16Ut
TLSHT1A6711FCDB7EF483A2A401694DF17A48E7D7EDC11090AC539DC18924B283CEEE85A0DB6
hashlookup:parent-total2
hashlookup:trust60

Network graph view

Parents (Total: 2)

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

Key Value
MD5553AC7339233234A7316FA30D6D18E75
PackageArchnoarch
PackageDescriptionThis package contains code which implements the Kubernetes "apply" operation. This package contains the source code needed for building packages that reference the following Go import paths: – sigs.k8s.io/structured-merge-diff
PackageMaintainerFedora Project
PackageNamegolang-sigs-k8s-structured-merge-diff-devel
PackageRelease3.fc33
PackageVersion3.0.0
SHA-13035F531DE9E22C26BC8C6E7553F7E99665B0DDE
SHA-2561D3EEE880D24EB7A8DFBEDF8D4D8B4C96788FD05C76B1BDE4244389B6F971DBE
Key Value
FileSize109652
MD526530A5FA39B04D510C7AF9DFBD01D72
PackageDescriptionimplementation for "server-side apply" (library) What is the apply operation? . It models resources in a control plane as having multiple "managers". Each manager is typically trying to manage only one aspect of a resource. The goal is to make it easy for disparate managers to make the changes they need without messing up the things that other managers are doing. In this system, both humans and machines (aka "controllers") act as managers. . To do this, it explicitly tracks (using the fieldset data structure) which fields each manager is currently managing. . Now, there are two basic mechanisms by which one modifies an object. . PUT/PATCH: This is a write command that says: "Make the object look EXACTLY like X". . APPLY: This is a write command that says: "The fields I manage should now look exactly like this (but I don't care about other fields)". . For PUT/PATCH, it deduces which fields will be managed based on what is changing. For APPLY, the user is explicitly stating which fields they wish to manage (and therefore requesting deletion of any fields that they used to manage but stop mentioning). . Any time a manager begins managing some new field, that field is removed from all other managers. If the manager is using the APPLY command, it calls these conflicts, and will not proceed unless the user passes the "force" option. This prevents accidentally setting fields which some other entity is managing. . PUT/PATCH always "force". They are mostly used by automated systems, which won't do anything productive with a new error type.
PackageMaintainerUbuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageNamegolang-k8s-sigs-structured-merge-diff-dev
PackageSectiondevel
PackageVersion3.0.0+ds1-2
SHA-10D51EFF8730ADCE8EAA4C42A117A00FBB0740F92
SHA-2560402618ABC29206817D5C2FEA79C3E1AFE031530A2797F931839C282912CE0AE