Result for 00112CEAC79FCCDA30675EC5080DE91A859451CB

Query result

Key Value
FileName./usr/share/gocode/src/sigs.k8s.io/structured-merge-diff/internal/testdata/k8s-deployment.yaml
FileSize4688
MD5D8BCFB2994FED495E5A04A7DB244B6DE
SHA-100112CEAC79FCCDA30675EC5080DE91A859451CB
SHA-256CA34BF1735629DF20D2DB45160704DD781C13AFC5CC41E69A93899591E8B686E
SSDEEP96:zI5bH775ToqK/AX94m28vuHCGS2UGusGNlzRmy/jDqlneGJSa9q8:WXKJm28vuHdvMNmnJI8
TLSHT1BDA13183AE4550FAF52CE5694AF8B203A62DF84BD0523D7C34DED7483F4A0EDA1C56A4
hashlookup:parent-total4
hashlookup:trust70

Network graph view

Parents (Total: 4)

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

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
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
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
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