github-vet / github-vet/rangeloop-pointer-findings
sapcc/kubernetes-operators: example/vendor/k8s.io/client-go/1.4/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 [sapcc/kubernetes-operators](https://www.github.com/sapcc/kubernetes-operators) at [example/vendor/k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1/types.generated.go](https://github.com/sapcc/kubernetes-operators/blob/2b57d5e733ae5b07f996c40f20b3faf9fab7e4cd/example/vendor/k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1/types.generated.go#L21984-L21988)
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 yyv1807 is reassigned at line 21986
[Click here to see the code in its original context.](https://github.com/sapcc/kubernetes-operators/blob/2b57d5e733ae5b07f996c40f20b3faf9fab7e4cd/example/vendor/k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1/types.generated.go#L21984-L21988)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv1807 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy1808 := &yyv1807
yy1808.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: 2b57d5e733ae5b07f996c40f20b3faf9fab7e4cd
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with example/vendor/k8s.io/client-go/1.4/pkg/apis/extensions/v1beta1/types.generated.go at lines 21984-21988 and inspect the range-loop reference described by the analyzer. Determine whether the reported reassignment is a bug, mitigated, or desirable behavior, then leave the corresponding reaction on the issue; no code change or test is specified.
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
- Needs clarification
- Newbie friendliness
- 25/100