github-vet / github-vet/rangeloop-pointer-findings
shadab005/ds-mit: src/mapreduce/common_map.go; 4 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [shadab005/ds-mit](https://www.github.com/shadab005/ds-mit) at [src/mapreduce/common_map.go](https://github.com/shadab005/ds-mit/blob/296387a63e2d97a8677303d04bda9713855ee5ca/src/mapreduce/common_map.go#L72-L75)
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/shadab005/ds-mit/blob/296387a63e2d97a8677303d04bda9713855ee5ca/src/mapreduce/common_map.go#L72-L75)
Click here to show the 4 line(s) of Go which triggered the analyzer.
```go
for _, kv := range keyValList {
// Now write this kv to intermediate file (with name given by reduceName(jobName, mapTask, r)
fileHandle[ihash(kv.Key)%nReduce].Encode(&kv)
}
```
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 {Encode 1} 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: 296387a63e2d97a8677303d04bda9713855ee5ca
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with src/mapreduce/common_map.go around lines 72-75 and read the surrounding MapReduce code to understand how the range variable is passed to Encode. Check the linked commit context and determine whether this instance is a bug, mitigated, or desirable behavior. Done means leaving the reaction that matches the evidence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100