rajatchopra/ose-contiv: contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go; 5 LoC

Open Beginner friendly
#14,650 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Open contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go around lines 47304-47308 and review the reported range-loop reference reassignment. Compare the snippet with the linked range-loop finding guidance, then leave a reaction classifying it as Bug, Mitigated, or Desirable Behavior.

Written by the indexing model from the issue text.

Description

fresh tiny

Found a possible issue in rajatchopra/ose-contiv at contrib/compare/Godeps/_workspace/src/k8s.io/kubernetes/pkg/api/types.generated.go

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 yyv3741 is reassigned at line 47306

Click here to see the code in its original context.

Click here to show the 5 line(s) of Go which triggered the analyzer.
	for _, yyv3741 := range v {
		z.EncSendContainerState(codecSelfer_containerArrayElem1234)
		yy3742 := &yyv3741
		yy3742.CodecEncodeSelf(e)
	}

Leave a reaction on this issue to contribute to the project by classifying this instance as a Bug 👎, Mitigated 👍, or Desirable Behavior 🚀
See the descriptions of the classifications here for more information.

commit ID: 0ff48115e6ad617b8937922bdb91eac89186b8f7

Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
PR metrics pending

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github-vet/rangeloop-pointer-findings

All issues in github-vet/rangeloop-pointer-findings

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.