github-vet / github-vet/rangeloop-pointer-findings
mlab-lattice/lattice: pkg/backend/kubernetes/controller/job/informer_event_handlers.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [mlab-lattice/lattice](https://www.github.com/mlab-lattice/lattice) at [pkg/backend/kubernetes/controller/job/informer_event_handlers.go](https://github.com/mlab-lattice/lattice/blob/8ad7070f7c0c5d2a24373b59567797afd669201f/pkg/backend/kubernetes/controller/job/informer_event_handlers.go#L193-L195)
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/mlab-lattice/lattice/blob/8ad7070f7c0c5d2a24373b59567797afd669201f/pkg/backend/kubernetes/controller/job/informer_event_handlers.go#L193-L195)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, service := range jobs {
c.enqueue(&service)
}
```
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 {enqueue 1} 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: 8ad7070f7c0c5d2a24373b59567797afd669201f
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with pkg/backend/kubernetes/controller/job/informer_event_handlers.go around lines 193-195, then trace enqueue and the surrounding informer handler. Determine whether passing the range variable address creates a real issue, and classify the finding as Bug, Mitigated, or Desirable Behavior as requested by the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend, infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100