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,684 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#L48534-L48538)

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 yyv3804 is reassigned at line 48536

[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#L48534-L48538)

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

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

Open contrib/diurnal/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go at lines 48534-48538 and review the range-loop reference shown in the issue. Read the linked classification descriptions, decide whether the finding is a Bug, Mitigated, or Desirable Behavior, and leave the corresponding reaction; completion is the reaction.

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
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.