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 port used in defer or goroutine at line 166
Click here to show the 21 line(s) of Go which triggered the analyzer.
```go
for _, port := range ports {
wg.Add(1)
go func(p int, wg *sync.WaitGroup) {
done := make(chan struct{})
s.jobChan <- portJob{
open: openChan,
closed: closedChan,
filtered: filteredChan,
ip: host,
port: p,
done: done,
ctx: ctx,
}
<-done
wg.Done()
}(port, wg)
}
```
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 for more information.
Found a possible issue in kalexmills/bad-go at scan-connect.go
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.
Click here to show the 21 line(s) of Go which triggered the analyzer.
```go for _, port := range ports { wg.Add(1) go func(p int, wg *sync.WaitGroup) { done := make(chan struct{}) s.jobChan <- portJob{ open: openChan, closed: closedChan, filtered: filteredChan, ip: host, port: p, done: done, ctx: ctx, } <-done wg.Done() }(port, wg) } ```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 for more information.
commit ID: a77b7b189ae6bb863a0ec1186f6fd12e1ec2a0a4