Result for 0B46CCA2380943E952EC4322B65C13090A1E44EB

Query result

Key Value
FileName./usr/share/gocode/src/sigs.k8s.io/structured-merge-diff/fieldpath/serialize-pe_test.go
FileSize2100
MD5825FBDD99853556D0F881CC663289692
SHA-10B46CCA2380943E952EC4322B65C13090A1E44EB
SHA-2568A99E684EFB91AA3B2A24EFBE66E2866BD6B7B4835CFE83C5ACFC5D2C67ACBDF
SSDEEP48:R+4+h0CH31KHMSahYnyXtmRmUSu0mhL5y3gVuhBRnyXpwjP:R+4s3HFKHuCwuCAhLKgQ/c+
TLSHT11D41255CF70B075707C1148D1C1EC8CF41AED8EBC41099EBA9CCA79B10A88AF156C994
hashlookup:parent-total7
hashlookup:trust85

Network graph view

Parents (Total: 7)

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

Key Value
MD57ED02643408C80C6B87C55933F3BF4FD
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
PackageMaintainerumeabot <umeabot>
PackageNamegolang-sigs-k8s-structured-merge-diff-devel
PackageRelease2.mga9
PackageVersion4.2.1
SHA-180DE8AB1A93FE9D31CCD014395B43E9D698BC05B
SHA-25625465089A96CBECDD456B80FD3CED095BA753FF34BB888992DCC757B37735A70
Key Value
FileSize116408
MD555239887437239F513E120E21BDE0454
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.
PackageMaintainerDebian Go Packaging Team <team+pkg-go@tracker.debian.org>
PackageNamegolang-k8s-sigs-structured-merge-diff-dev
PackageSectiondevel
PackageVersion4.0.2+ds1-2
SHA-1C6BA04E321760C2D10F5C3D220FD7573F18600A3
SHA-256871B2DD766A472B69D3F5871578633B1FF72E9A13246BE487C6AFF8C561FB04F
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
Key Value
MD5199675B74DD5F7EEA8EDC18975E01ADC
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
PackageRelease2.fc34
PackageVersion4.0.2
SHA-15B48EC7DC82AB322BC581C7E01F69DAC86B0A77B
SHA-256E9875435CBB429656EAACA3A0F319CBB12BAE46A54C46108F051CD7293FAE490
Key Value
FileSize121920
MD58EA5CEF057336C28C9616EDED71B9E5C
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.
PackageMaintainerDebian Go Packaging Team <team+pkg-go@tracker.debian.org>
PackageNamegolang-k8s-sigs-structured-merge-diff-dev
PackageSectiondevel
PackageVersion4.1.2+ds1-1
SHA-13B9CEF2188175AABC2822A8286ACFAAB1AF7B8BC
SHA-25622F38F870A63BFAED0686C9F37652D420C195231ECDBD97B076567705659FD90
Key Value
FileSize116452
MD5D6082ED60CC1DC4409149F47943926E4
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
PackageVersion4.0.2+ds1-2
SHA-183602751405893F9FB378AEC58AD38528AC0ED7F
SHA-2566C8E8BE703229C5CDCB0E8FF81397F9F55B964C85DAAEA8EF9A75F64AD68569D