Result for 08C42A40D2CD049FD41B07E7555D071DD0FD5647

Query result

Key Value
FileName./usr/share/gocode/src/sigs.k8s.io/structured-merge-diff/internal/testdata/endpoints.yaml
FileSize188334
MD56E73CCAB46A68EFBE9163007FB90F452
SHA-108C42A40D2CD049FD41B07E7555D071DD0FD5647
SHA-256B7F721E3C0C2086A08B6BCC36BD20054B5193D75FF5B318FC9366ADDACA01D3C
SSDEEP384:C/aVYL2x+D3SolqP0BGbAdd6LHi5szelom7UhKvIF+TT+ZMnC9g7mcpOjwNS3kxH:s40YqJY/etcjCR
TLSHT10C048F92A865C986C356C0B624757B1E80710F7B6162363FFCDDABC49F834726783B62
hashlookup:parent-total5
hashlookup:trust75

Network graph view

Parents (Total: 5)

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

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
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
MD508C2DCFC19B3DCD23DE7B40C87B89FAA
PackageArchnoarch
PackageDescriptionKubernetes is an open source system for managing containerized applications across multiple hosts; providing basic mechanisms for deployment, maintenance, and scaling of applications. Kubernetes builds upon a decade and a half of experience at Google running production workloads at scale using a system called Borg, combined with best-of-breed ideas and practices from the community. This package contains the source code needed for building packages that reference the following Go import paths: – k8s.io/kubernetes
PackageMaintainerFedora Project
PackageNamegolang-k8s-kubernetes-devel
PackageRelease2.fc33~bootstrap
PackageVersion1.18.3
SHA-1238A10F9D4166A4D76AD907C20AABC20BDCE8BAC
SHA-25677F442C005E65421F6A8C43B932B22499B50C804F9915412BBD80F72C3C7D290
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