github-vet / github-vet/rangeloop-pointer-findings
marcusdeng22/kubernetes_test: diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go; 5 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [marcusdeng22/kubernetes_test](https://www.github.com/marcusdeng22/kubernetes_test) at [diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go](https://github.com/marcusdeng22/kubernetes_test/blob/3ddd47a9905cb45e7632c207bad3fdef64bc45c6/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L46897-L46901)
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.
> reference to yyv3710 is reassigned at line 46899
[Click here to see the code in its original context.](https://github.com/marcusdeng22/kubernetes_test/blob/3ddd47a9905cb45e7632c207bad3fdef64bc45c6/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L46897-L46901)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv3710 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3711 := &yyv3710
yy3711.CodecEncodeSelf(e)
}
```
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: 3ddd47a9905cb45e7632c207bad3fdef64bc45c6
Contributor guide
No contributing guide indexed for this repository
Research direction
Read diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 46897-46901 and inspect the range loop shown in the report. Determine whether the reference to yyv3710 represents a real range-loop pointer issue, then use the issue's Bug, Mitigated, or Desirable Behavior reaction to classify it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100