kubevirt.io/kubevirt/tests/libkubevirt.GetCurrentKv
third-partyThe 3981st most-called third-party function by production calls. Called 189 times across 2 modules; 149 of those run outside tests and generated code.
All of kubevirt.io/kubevirt/tests/libkubevirt → Docs on pkg.go.dev ↗
- prod calls
- 149
- non-test, non-generated
- all calls
- 189
- total callsites
- modules
- 2
- distinct callers
- in loop
- 0%
- of prod calls
- in tests
- 21%
- 40 calls
- resolved
- 100%
- to a known target
resolution mix
How each call resolves
How each call was attributed. Only resolved kinds, where the target function is known, count toward the ranking. Interface dispatch and unresolved receivers are reported separately and never guessed. Read the taxonomy →
- Package function50%A direct call to an exported package function, resolved by type.
- Package function (by syntax)50%A package function in a module outside the crawl, keyed by import path.
who calls this
Notable callers
Production calls into GetCurrentKv from notable Go projects. Open one on the map to see what else it hammers.
- KubeVirt 74 50%
where it's called
Callsites in the wild
12 representative callsites of 189, prioritizing in-loop and non-test usage. We link to source, never display it.
-
-
kubevirt.io/kubevirt @v1.9.0
tests/libhypervisor/hypervisor.go:14
-
-
kubevirt.io/kubevirt @v1.9.0
tests/testsuite/runconfiguration.go:19
-
-
kubevirt.io/kubevirt @v1.9.0
tests/instancetype/memory_overcommit.go:37
-
-
kubevirt.io/kubevirt @v1.9.0
tests/libkubevirt/config/featuregate.go:38
-
-
kubevirt.io/kubevirt @v1.9.0
tests/instancetype/reference_policy.go:38
-
-
kubevirt.io/kubevirt @v1.9.0
tests/infrastructure/cluster-profiler.go:40
top callers
The modules that reach for it
The modules that call GetCurrentKv most in this snapshot.
- kubevirt.io/kubevirt9550%
- github.com/kubevirt/kubevirt9450%