github-vet / github-vet/rangeloop-pointer-findings

oneinfra/oneinfra: apis/infra/v1alpha1/zz_generated.deepcopy.go; 13 LoC

Open
#17,889 0 comments 0 reactions 0 assignees View on GitHub
fresh small
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
PR metrics pending

Description

Found a possible issue in [oneinfra/oneinfra](https://www.github.com/oneinfra/oneinfra) at [apis/infra/v1alpha1/zz_generated.deepcopy.go](https://github.com/oneinfra/oneinfra/blob/37af1ef3827d56cbd4172185168b2fe7aa02c3c2/apis/infra/v1alpha1/zz_generated.deepcopy.go#L40-L52)

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 45

[Click here to see the code in its original context.](https://github.com/oneinfra/oneinfra/blob/37af1ef3827d56cbd4172185168b2fe7aa02c3c2/apis/infra/v1alpha1/zz_generated.deepcopy.go#L40-L52)

Click here to show the 13 line(s) of Go which triggered the analyzer.

```go
for key, val := range *in {
var outVal map[string]string
if val == nil {
(*out)[key] = nil
} else {
in, out := &val, &outVal
*out = make(FileMap, len(*in))
for key, val := range *in {
(*out)[key] = val
}
}
(*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: 37af1ef3827d56cbd4172185168b2fe7aa02c3c2

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with apis/infra/v1alpha1/zz_generated.deepcopy.go at lines 40-52 and inspect the reported range-loop references in commit 37af1ef3827d56cbd4172185168b2fe7aa02c3c2. Compare the analyzer warning with Go range-loop behavior and the surrounding generated deepcopy logic. Done means reacting to classify the finding as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.