github-vet / github-vet/rangeloop-pointer-findings
nak3/kubernetes-manifest-scanner: Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go; 5 LoC
- 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/api/types.generated.go](https://github.com/nak3/kubernetes-manifest-scanner/blob/d5cc57db0face3457961c9d05398ffa0271b4ccb/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go#L46030-L46034)
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 yyv3623 is reassigned at line 46032
[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/api/types.generated.go#L46030-L46034)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv3623 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3624 := &yyv3623
yy3624.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
Open Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 46030-46034 and review the reported range-loop reference reassignment in context. Use the issue’s linked classification descriptions to decide whether this instance is a Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100