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

kubernetes-retired/contrib: diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go; 5 LoC

Open
#15,417 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 [kubernetes-retired/contrib](https://www.github.com/kubernetes-retired/contrib) at [diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go](https://github.com/kubernetes-retired/contrib/blob/89f6948e24578fed2a90a87871b2263729f90ac3/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L44809-L44813)

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 yyv3602 is reassigned at line 44811

[Click here to see the code in its original context.](https://github.com/kubernetes-retired/contrib/blob/89f6948e24578fed2a90a87871b2263729f90ac3/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L44809-L44813)

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

```go
for _, yyv3602 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3603 := &yyv3602
yy3603.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: 89f6948e24578fed2a90a87871b2263729f90ac3

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 44809-44813 and inspect the reported range-loop reference reassignment. Compare the analyzer finding with the surrounding generated code and determine whether it should be classified as 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
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.