github-vet / github-vet/rangeloop-pointer-findings
zigmahq/zigma: dht/mock_rpc.go; 9 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [zigmahq/zigma](https://www.github.com/zigmahq/zigma) at [dht/mock_rpc.go](https://github.com/zigmahq/zigma/blob/8db6c85b1e6001437b2f97a5c7fb4f25385a1a65/dht/mock_rpc.go#L56-L64)
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.
> range-loop variable r used in defer or goroutine at line 58
[Click here to see the code in its original context.](https://github.com/zigmahq/zigma/blob/8db6c85b1e6001437b2f97a5c7fb4f25385a1a65/dht/mock_rpc.go#L56-L64)
Click here to show the 9 line(s) of Go which triggered the analyzer.
```go
for _, r := range mrpcs.rpcs {
if r.self.Equal(msg.Receiver) {
go func() { r.receive <- msg }()
if d, ok := r.replies.Load(id); ok && len(id) > 0 && msg.IsResponse {
go func() { d.(chan *Message) <- msg }()
}
break
}
}
```
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: 8db6c85b1e6001437b2f97a5c7fb4f25385a1a65
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.