github-vet / github-vet/rangeloop-pointer-findings
CuiZhicheng/calico-for-lxc: cni-plugin/vendor/k8s.io/client-go/pkg/apis/rbac/v1alpha1/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 [CuiZhicheng/calico-for-lxc](https://www.github.com/CuiZhicheng/calico-for-lxc) at [cni-plugin/vendor/k8s.io/client-go/pkg/apis/rbac/v1alpha1/types.generated.go](https://github.com/CuiZhicheng/calico-for-lxc/blob/7cade7fcab86820d9633a9ff6ffb53ca52eceb3e/cni-plugin/vendor/k8s.io/client-go/pkg/apis/rbac/v1alpha1/types.generated.go#L4342-L4346)
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 yyv372 is reassigned at line 4344
[Click here to see the code in its original context.](https://github.com/CuiZhicheng/calico-for-lxc/blob/7cade7fcab86820d9633a9ff6ffb53ca52eceb3e/cni-plugin/vendor/k8s.io/client-go/pkg/apis/rbac/v1alpha1/types.generated.go#L4342-L4346)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv372 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy373 := &yyv372
yy373.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: 7cade7fcab86820d9633a9ff6ffb53ca52eceb3e
Contributor guide
No contributing guide indexed for this repository
Research direction
Read cni-plugin/vendor/k8s.io/client-go/pkg/apis/rbac/v1alpha1/types.generated.go around lines 4342-4346 and inspect the reported range-loop reference. Determine whether the analyzer finding is a Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction on the issue.
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
- 42/100