github-vet / github-vet/rangeloop-pointer-findings
open-cluster-management/multicloud-operators-subscription: pkg/apis/apps/v1/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 [open-cluster-management/multicloud-operators-subscription](https://www.github.com/open-cluster-management/multicloud-operators-subscription) at [pkg/apis/apps/v1/zz_generated.deepcopy.go](https://github.com/open-cluster-management/multicloud-operators-subscription/blob/9b20f309865dbe08e040f41a2e52f2fe97ad09aa/pkg/apis/apps/v1/zz_generated.deepcopy.go#L274-L284)
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 279
[Click here to see the code in its original context.](https://github.com/open-cluster-management/multicloud-operators-subscription/blob/9b20f309865dbe08e040f41a2e52f2fe97ad09aa/pkg/apis/apps/v1/zz_generated.deepcopy.go#L274-L284)
Click here to show the 11 line(s) of Go which triggered the analyzer.
```go
for key, val := range *in {
var outVal *SubscriptionUnitStatus
if val == nil {
(*out)[key] = nil
} else {
in, out := &val, &outVal
*out = new(SubscriptionUnitStatus)
(*in).DeepCopyInto(*out)
}
(*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: 9b20f309865dbe08e040f41a2e52f2fe97ad09aa
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked 11-line snippet in pkg/apis/apps/v1/zz_generated.deepcopy.go and inspect the surrounding generated deepcopy implementation. Determine whether the reported range-loop reference reassignment affects the copied value, then leave the appropriate Bug, Mitigated, or Desirable Behavior reaction as the completed result.
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
- 45/100