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#L43953-L43957)
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 yyv3512 is reassigned at line 43955
[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#L43953-L43957)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, yyv3512 := range v {
z.EncSendContainerState(codecSelfer_containerArrayElem1234)
yy3513 := &yyv3512
yy3513.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
Read Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 43953-43957 and review the linked analyzer context. Determine whether the range-loop pointer finding is a bug, mitigated, or desirable behavior, then leave the corresponding reaction; completion is the classification reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100