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

marcusdeng22/kubernetes_test: diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go; 5 LoC

Open
#17,275 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 [marcusdeng22/kubernetes_test](https://www.github.com/marcusdeng22/kubernetes_test) at [diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go](https://github.com/marcusdeng22/kubernetes_test/blob/3ddd47a9905cb45e7632c207bad3fdef64bc45c6/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go#L48194-L48198)

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 yyv3778 is reassigned at line 48196

[Click here to see the code in its original context.](https://github.com/marcusdeng22/kubernetes_test/blob/3ddd47a9905cb45e7632c207bad3fdef64bc45c6/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go#L48194-L48198)

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

```go
for _, yyv3778 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3779 := &yyv3778
yy3779.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: 3ddd47a9905cb45e7632c207bad3fdef64bc45c6

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go at lines 48194-48198 and inspect the range loop and pointer use. Consult the linked classification descriptions, then determine whether the analyzer finding is a Bug, Mitigated, or Desirable Behavior and leave the corresponding reaction; that classification is the done condition.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.