github-vet / github-vet/rangeloop-pointer-findings
JargoonPard/appGatewaySample: kubernetes/vendor/k8s.io/kubernetes/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 [JargoonPard/appGatewaySample](https://www.github.com/JargoonPard/appGatewaySample) at [kubernetes/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go](https://github.com/JargoonPard/appGatewaySample/blob/809b1737d6442418cd84e2f66fa8566a0247ec34/kubernetes/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go#L22312-L22316)
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 yyv1829 is reassigned at line 22314
[Click here to see the code in its original context.](https://github.com/JargoonPard/appGatewaySample/blob/809b1737d6442418cd84e2f66fa8566a0247ec34/kubernetes/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go#L22312-L22316)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv1829 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy1830 := &yyv1829
yy1830.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: 809b1737d6442418cd84e2f66fa8566a0247ec34
Contributor guide
No contributing guide indexed for this repository
Research direction
Read kubernetes/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go around lines 22312-22316 and review the reported range-loop reference reassignment. Compare the snippet with the linked classification guidance, then react with Bug, Mitigated, or Desirable Behavior; done means recording the classification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100