github-vet / github-vet/rangeloop-pointer-findings
rajatchopra/ose-contiv: contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/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/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go](https://github.com/rajatchopra/ose-contiv/blob/0ff48115e6ad617b8937922bdb91eac89186b8f7/contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go#L45041-L45045)
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 yyv3609 is reassigned at line 45043
[Click here to see the code in its original context.](https://github.com/rajatchopra/ose-contiv/blob/0ff48115e6ad617b8937922bdb91eac89186b8f7/contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go#L45041-L45045)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv3609 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3610 := &yyv3609
yy3610.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
Inspect contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go around lines 45041-45045 and read the linked range-loop context. Determine whether taking the address of yyv3609 creates an unintended loop-variable reference, then classify the finding as Bug, Mitigated, or Desirable Behavior with the corresponding issue 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
- Mostly clear
- Newbie friendliness
- 35/100