github-vet / github-vet/rangeloop-pointer-findings
renproject/mpc: rng/rng.go; 9 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [renproject/mpc](https://www.github.com/renproject/mpc) at [rng/rng.go](https://github.com/renproject/mpc/blob/71f4e68af86fbd95962cbe3424e49127a0a9ee22/rng/rng.go#L134-L142)
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.
>
[Click here to see the code in its original context.](https://github.com/renproject/mpc/blob/71f4e68af86fbd95962cbe3424e49127a0a9ee22/rng/rng.go#L134-L142)
Click here to show the 9 line(s) of Go which triggered the analyzer.
```go
for _, j := range indices {
for _, setOfShares := range brngShareBatch {
accShare := compute.ShareOfShare(j, setOfShares)
if isZero {
accShare.Scale(&accShare, &j)
}
directedOpenings[j] = append(directedOpenings[j], accShare)
}
}
```
Click here to show extra information the analyzer produced.
```
No path was found through the callgraph that could lead to a function which writes a pointer argument.
No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.
root signature {Scale 2} was not found in the callgraph; reference was passed directly to third-party code
```
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: 71f4e68af86fbd95962cbe3424e49127a0a9ee22
Contributor guide
No contributing guide indexed for this repository
Research direction
Read rng/rng.go at lines 134-142, then inspect the surrounding range-loop code and the Scale call's context. Determine whether the analyzer finding represents a Bug, Mitigated case, or Desirable Behavior, and record the conclusion with the corresponding issue reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100