github-vet / github-vet/rangeloop-pointer-findings
senthilrch/kube-fledged: pkg/apis/kubefledged/v1alpha1/zz_generated.deepcopy.go; 11 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [senthilrch/kube-fledged](https://www.github.com/senthilrch/kube-fledged) at [pkg/apis/kubefledged/v1alpha1/zz_generated.deepcopy.go](https://github.com/senthilrch/kube-fledged/blob/33e62ec9d80027961165dd0c22d207c241db6c68/pkg/apis/kubefledged/v1alpha1/zz_generated.deepcopy.go#L151-L161)
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 val is reassigned at line 156
[Click here to see the code in its original context.](https://github.com/senthilrch/kube-fledged/blob/33e62ec9d80027961165dd0c22d207c241db6c68/pkg/apis/kubefledged/v1alpha1/zz_generated.deepcopy.go#L151-L161)
Click here to show the 11 line(s) of Go which triggered the analyzer.
```go
for key, val := range *in {
var outVal []NodeReasonMessage
if val == nil {
(*out)[key] = nil
} else {
in, out := &val, &outVal
*out = make(NodeReasonMessageList, len(*in))
copy(*out, *in)
}
(*out)[key] = outVal
}
```
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: 33e62ec9d80027961165dd0c22d207c241db6c68
Contributor guide
No contributing guide indexed for this repository
Research direction
Read pkg/apis/kubefledged/v1alpha1/zz_generated.deepcopy.go around lines 151-161 and inspect the reported range-loop variable reassignment in context. Determine whether the analyzer finding represents a bug, mitigated behavior, 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
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100