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

yingyan003/netChecker: src/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go; 5 LoC

Open
#17,418 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 [yingyan003/netChecker](https://www.github.com/yingyan003/netChecker) at [src/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go](https://github.com/yingyan003/netChecker/blob/32661fc5ba586d9bdc17a756f570d45954caa996/src/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go#L23228-L23232)

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 yyv1897 is reassigned at line 23230

[Click here to see the code in its original context.](https://github.com/yingyan003/netChecker/blob/32661fc5ba586d9bdc17a756f570d45954caa996/src/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go#L23228-L23232)

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

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

Contributor guide

No contributing guide indexed for this repository

Research direction

Read the analyzer report and the linked context in src/vendor/k8s.io/kubernetes/pkg/apis/extensions/v1beta1/types.generated.go around lines 23228-23232. Compare the range-loop pointer pattern with the linked classification descriptions, then leave a reaction marking the finding as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.