github-vet / github-vet/rangeloop-pointer-findings
albertrdixon/romulus: 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 [albertrdixon/romulus](https://www.github.com/albertrdixon/romulus) at [Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go](https://github.com/albertrdixon/romulus/blob/5a0bf879172a8077a17d89589d4b35c81db13516/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go#L15953-L15957)
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 yyv1330 is reassigned at line 15955
[Click here to see the code in its original context.](https://github.com/albertrdixon/romulus/blob/5a0bf879172a8077a17d89589d4b35c81db13516/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go#L15953-L15957)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv1330 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy1331 := &yyv1330
yy1331.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: 5a0bf879172a8077a17d89589d4b35c81db13516
Contributor guide
No contributing guide indexed for this repository
Research direction
Read the referenced snippet in Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go around lines 15953-15957 and consider whether the range-variable reference is an actual problem. Check the linked code context and the analyzer’s classification guidance; done means leaving the appropriate Bug, Mitigated, or Desirable Behavior reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100