kubevirt.io/kubevirt/pkg/virt-controller/watch/common.NewSyncError
third-partyThe 3916th most-called third-party function by production calls. Called 154 times across 2 modules; 152 of those run outside tests and generated code.
All of kubevirt.io/kubevirt/pkg/virt-controller/watch/common → Docs on pkg.go.dev ↗
- prod calls
- 152
- non-test, non-generated
- all calls
- 154
- total callsites
- modules
- 2
- distinct callers
- in loop
- 9%
- of prod calls
- in tests
- 1%
- 2 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 NewSyncError from notable Go projects. Open one on the map to see what else it hammers.
- KubeVirt 76 50%
where it's called
Callsites in the wild
12 representative callsites of 154, prioritizing in-loop and non-test usage. We link to source, never display it.
- in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-controller/watch/vmi/volume-hotplug.go:120
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-controller/watch/vmi/datavolumes.go:134
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-controller/watch/vmi/volume-hotplug.go:185
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-controller/watch/vmi/volume-hotplug.go:194
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-controller/watch/vmi/lifecycle.go:988
in loop - in loop
-
kubevirt.io/kubevirt @v1.9.0
pkg/virt-controller/watch/pool/pool.go:1378
in loop
top callers
The modules that reach for it
The modules that call NewSyncError most in this snapshot.
- github.com/kubevirt/kubevirt7750%
- kubevirt.io/kubevirt7750%