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

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

Open
#14,668 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 [rajatchopra/ose-contiv](https://www.github.com/rajatchopra/ose-contiv) at [contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go](https://github.com/rajatchopra/ose-contiv/blob/0ff48115e6ad617b8937922bdb91eac89186b8f7/contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L47957-L47961)

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 yyv3770 is reassigned at line 47959

[Click here to see the code in its original context.](https://github.com/rajatchopra/ose-contiv/blob/0ff48115e6ad617b8937922bdb91eac89186b8f7/contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L47957-L47961)

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

```go
for _, yyv3770 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3771 := &yyv3770
yy3771.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: 0ff48115e6ad617b8937922bdb91eac89186b8f7

Contributor guide

No contributing guide indexed for this repository

Research direction

Inspect contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 47957-47961 and review the reported range-loop reference behavior in the five-line snippet. Decide whether the analyzer finding 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
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.