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

DavadDi/go_study: src/podWatch/vendor/k8s.io/client-go/pkg/api/v1/types.generated.go; 5 LoC

Open
#10,897 0 comments 0 reactions 0 assignees View on GitHub
fresh tiny
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
PR metrics pending

Description

Found a possible issue in [DavadDi/go_study](https://www.github.com/DavadDi/go_study) at [src/podWatch/vendor/k8s.io/client-go/pkg/api/v1/types.generated.go](https://github.com/DavadDi/go_study/blob/a80dad4fa8f92ef16c5e6d303f1e9e224ad4e15b/src/podWatch/vendor/k8s.io/client-go/pkg/api/v1/types.generated.go#L62613-L62617)

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 yyv4863 is reassigned at line 62615

[Click here to see the code in its original context.](https://github.com/DavadDi/go_study/blob/a80dad4fa8f92ef16c5e6d303f1e9e224ad4e15b/src/podWatch/vendor/k8s.io/client-go/pkg/api/v1/types.generated.go#L62613-L62617)

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

```go
for _, yyv4863 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy4864 := &yyv4863
yy4864.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: a80dad4fa8f92ef16c5e6d303f1e9e224ad4e15b

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect src/podWatch/vendor/k8s.io/client-go/pkg/api/v1/types.generated.go around lines 62613-62617 and read the linked analyzer guidance for range-loop findings. Determine whether the reported reference reassignment 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
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.