github-vet / github-vet/rangeloop-pointer-findings
rjchee/spongemock: cmd/worker/main.go; 14 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [rjchee/spongemock](https://www.github.com/rjchee/spongemock) at [cmd/worker/main.go](https://github.com/rjchee/spongemock/blob/5f0fcb1810c9e1224824e1733813e314f3282b09/cmd/worker/main.go#L47-L60)
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 p used in defer or goroutine at line 55
[Click here to see the code in its original context.](https://github.com/rjchee/spongemock/blob/5f0fcb1810c9e1224824e1733813e314f3282b09/cmd/worker/main.go#L47-L60)
Click here to show the 14 line(s) of Go which triggered the analyzer.
```go
for _, p := range plugins {
for _, v := range p.EnvVariables() {
v.Set()
}
ch := make(chan error)
go func(ch <-chan error) {
for err := range ch {
agg <- pluginError{p.Name(), err}
}
}(ch)
go p.Start(ch)
}
```
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: 5f0fcb1810c9e1224824e1733813e314f3282b09
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.