github-vet / github-vet/rangeloop-pointer-findings
kubernetes-retired/contrib: diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/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 [kubernetes-retired/contrib](https://www.github.com/kubernetes-retired/contrib) at [diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go](https://github.com/kubernetes-retired/contrib/blob/89f6948e24578fed2a90a87871b2263729f90ac3/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go#L15832-L15836)
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 yyv1274 is reassigned at line 15834
[Click here to see the code in its original context.](https://github.com/kubernetes-retired/contrib/blob/89f6948e24578fed2a90a87871b2263729f90ac3/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go#L15832-L15836)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv1274 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy1275 := &yyv1274
yy1275.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: 89f6948e24578fed2a90a87871b2263729f90ac3
Contributor guide
No contributing guide indexed for this repository
Research direction
Open diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go around lines 15832-15836 and inspect how the range variable is referenced. Decide whether the analyzer finding is a bug, mitigated, or desirable behavior, then record that classification with the corresponding reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100