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

albertrdixon/romulus: Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go; 5 LoC

Open
#15,994 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 [albertrdixon/romulus](https://www.github.com/albertrdixon/romulus) at [Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go](https://github.com/albertrdixon/romulus/blob/5a0bf879172a8077a17d89589d4b35c81db13516/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go#L48915-L48919)

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 yyv3835 is reassigned at line 48917

[Click here to see the code in its original context.](https://github.com/albertrdixon/romulus/blob/5a0bf879172a8077a17d89589d4b35c81db13516/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go#L48915-L48919)

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

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

Contributor guide

No contributing guide indexed for this repository

Research direction

Read Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/v1/types.generated.go around lines 48915-48919 and inspect how the range variable yyv3835 is referenced. Compare that behavior with the analyzer's range-loop finding, then classify the report by leaving the Bug, Mitigated, or Desirable Behavior reaction.

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.