github-vet / github-vet/rangeloop-pointer-findings
kubernetes/kubernetes: test/e2e/network/ingress.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [kubernetes/kubernetes](https://www.github.com/kubernetes/kubernetes) at [test/e2e/network/ingress.go](https://github.com/kubernetes/kubernetes/blob/0eea524c28ea4c0e4a0d2746184f3dc63ff124b9/test/e2e/network/ingress.go#L1149-L1151)
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.
>
[Click here to see the code in its original context.](https://github.com/kubernetes/kubernetes/blob/0eea524c28ea4c0e4a0d2746184f3dc63ff124b9/test/e2e/network/ingress.go#L1149-L1151)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, ing := range ings.Items {
expectFinalizer(&ing, "deleting ingress collection")
}
```
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.
No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.
root signature {expectFinalizer 2} was not found in the callgraph; reference was passed directly to third-party code
```
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: 0eea524c28ea4c0e4a0d2746184f3dc63ff124b9
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at test/e2e/network/ingress.go lines 1149-1151 and inspect the surrounding use of expectFinalizer and the range variable. Determine whether the analyzer finding represents a real issue, a mitigated case, or desirable behavior; done means recording one of those classifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100