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#L16881-L16885)
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 yyv1378 is reassigned at line 16883
[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#L16881-L16885)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv1378 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy1379 := &yyv1378
yy1379.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
Inspect Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go around lines 16881-16885 and review the reported range-loop pointer reference. Determine whether the analyzer finding represents a bug, mitigated behavior, or desirable behavior, then classify the issue with the corresponding reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100