Vincoll/vigie: pkg/probe/port/portfunc.go; 12 LoC

Found a possible issue in [Vincoll/vigie](https://www.github.com/Vincoll/vigie) at [pkg/probe/port/portfunc.go](https://github.com/Vincoll/vigie/blob/24706fe588dcac28076988bf4fa367e66863beb6/pkg/probe/port/portfunc.go#L39-L50)

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 hp used in defer or goroutine at line 42

[Click here to see the code in its original context.](https://github.com/Vincoll/vigie/blob/24706fe588dcac28076988bf4fa367e66863beb6/pkg/probe/port/portfunc.go#L39-L50)

Click here to show the 12 line(s) of Go which triggered the analyzer.

```go
for i, hp := range addrsPort {

go func() {
pa, errReq := sendPortRequest(hp, p.Protocol, timeout)
if errReq != nil {
pi := probe.ProbeInfo{Status: probe.Error, Error: errReq.Error()}
pa = ProbeAnswer{Reachable: false, ProbeInfo: pi}
}
probeAnswers[i] = &pa
wg.Done()
}()
}

```

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: 24706fe588dcac28076988bf4fa367e66863beb6

Open pkg/probe/port/portfunc.go around lines 39-50 and inspect how the goroutine uses the range variables hp and i. Read the surrounding probing code and check whether concurrent execution can produce incorrect addresses or result indexes. Classify the finding with the appropriate reaction based on the observed behavior.

Written by the indexing model from the issue text.