github-vet / github-vet/rangeloop-pointer-findings
dailymotion/oplog: cmd/oplog-sync/main.go; 4 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [dailymotion/oplog](https://www.github.com/dailymotion/oplog) at [cmd/oplog-sync/main.go](https://github.com/dailymotion/oplog/blob/5e917148151518ee2e07bf8daad1110d7b9ed460/cmd/oplog-sync/main.go#L124-L127)
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 obd is reassigned at line 125
[Click here to see the code in its original context.](https://github.com/dailymotion/oplog/blob/5e917148151518ee2e07bf8daad1110d7b9ed460/cmd/oplog-sync/main.go#L124-L127)
Click here to show the 4 line(s) of Go which triggered the analyzer.
```go
for _, obd := range opMap {
op.Data = &obd
ops <- op
}
```
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: 5e917148151518ee2e07bf8daad1110d7b9ed460
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.