github-vet / github-vet/rangeloop-pointer-findings
atombender/ktail: controller.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [atombender/ktail](https://www.github.com/atombender/ktail) at [controller.go](https://github.com/atombender/ktail/blob/f7f8648c7b2b661c0e0f9b1f11c076fc18e4dc12/controller.go#L163-L165)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.
> function call at line 164 passes reference to container to third-party code
[Click here to see the code in its original context.](https://github.com/atombender/ktail/blob/f7f8648c7b2b661c0e0f9b1f11c076fc18e4dc12/controller.go#L163-L165)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, container := range pod.Spec.Containers {
ctl.deleteContainer(pod, &container)
}
```
Click here to show extra information the analyzer produced.
```
No path was found through the callgraph that could lead to a function which writes a pointer argument.
The following graphviz dot graph describes paths through the callgraph that could lead to a function which passes a pointer to third-party code:
digraph G {
"(deleteContainer, 2)" -> {}
}
```
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: f7f8648c7b2b661c0e0f9b1f11c076fc18e4dc12
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.