github-vet / github-vet/rangeloop-pointer-findings
rajatchopra/ose-contiv: contrib/compare/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 [rajatchopra/ose-contiv](https://www.github.com/rajatchopra/ose-contiv) at [contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go](https://github.com/rajatchopra/ose-contiv/blob/0ff48115e6ad617b8937922bdb91eac89186b8f7/contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L47766-L47770)
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 yyv3769 is reassigned at line 47768
[Click here to see the code in its original context.](https://github.com/rajatchopra/ose-contiv/blob/0ff48115e6ad617b8937922bdb91eac89186b8f7/contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L47766-L47770)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv3769 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3770 := &yyv3769
yy3770.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: 0ff48115e6ad617b8937922bdb91eac89186b8f7
Contributor guide
No contributing guide indexed for this repository
Research direction
Read contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 47766-47770 and the linked analyzer context first. Determine whether the range-variable reference is a bug, mitigated, or desirable behavior; done means leaving the requested reaction classification on the issue.
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
- Mostly clear
- Newbie friendliness
- 32/100