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

nak3/kubernetes-manifest-scanner: Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go; 5 LoC

Open
#16,416 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 [nak3/kubernetes-manifest-scanner](https://www.github.com/nak3/kubernetes-manifest-scanner) at [Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go](https://github.com/nak3/kubernetes-manifest-scanner/blob/d5cc57db0face3457961c9d05398ffa0271b4ccb/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go#L14728-L14732)

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 yyv1187 is reassigned at line 14730

[Click here to see the code in its original context.](https://github.com/nak3/kubernetes-manifest-scanner/blob/d5cc57db0face3457961c9d05398ffa0271b4ccb/Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go#L14728-L14732)

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

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

Contributor guide

No contributing guide indexed for this repository

Research direction

Read Godeps/_workspace/src/k8s.io/kubernetes/pkg/apis/extensions/types.generated.go around lines 14728-14732 and inspect the surrounding generated code to understand the reported range-loop reference. Determine whether the analyzer finding is a bug, mitigated, or desirable behavior, then leave the corresponding reaction as requested.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.