github-vet / github-vet/rangeloop-pointer-findings
DavadDi/go_study: src/podWatch/vendor/k8s.io/client-go/pkg/apis/extensions/v1beta1/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 [DavadDi/go_study](https://www.github.com/DavadDi/go_study) at [src/podWatch/vendor/k8s.io/client-go/pkg/apis/extensions/v1beta1/types.generated.go](https://github.com/DavadDi/go_study/blob/a80dad4fa8f92ef16c5e6d303f1e9e224ad4e15b/src/podWatch/vendor/k8s.io/client-go/pkg/apis/extensions/v1beta1/types.generated.go#L19580-L19584)
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 yyv1623 is reassigned at line 19582
[Click here to see the code in its original context.](https://github.com/DavadDi/go_study/blob/a80dad4fa8f92ef16c5e6d303f1e9e224ad4e15b/src/podWatch/vendor/k8s.io/client-go/pkg/apis/extensions/v1beta1/types.generated.go#L19580-L19584)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv1623 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy1624 := &yyv1623
yy1624.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: a80dad4fa8f92ef16c5e6d303f1e9e224ad4e15b
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/podWatch/vendor/k8s.io/client-go/pkg/apis/extensions/v1beta1/types.generated.go at lines 19580-19584 and review the linked commit context. Consult the classification descriptions in the issue to assess the analyzer finding about yyv1623, then leave the appropriate reaction when the behavior is understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100