jxaas/jxaas: core/huddle.go; 4 LoC

Found a possible issue in [jxaas/jxaas](https://www.github.com/jxaas/jxaas) at [core/huddle.go](https://github.com/jxaas/jxaas/blob/985f9a2814e08077b7ee113eae0e4c1568bfdb09/core/huddle.go#L417-L420)

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 unitStatus is reassigned at line 419

[Click here to see the code in its original context.](https://github.com/jxaas/jxaas/blob/985f9a2814e08077b7ee113eae0e4c1568bfdb09/core/huddle.go#L417-L420)

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

```go
for _, unitStatus := range serviceStatus.Units {
machineId := unitStatus.Machine
unitsByMachine[machineId] = &unitStatus
}

```

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: 985f9a2814e08077b7ee113eae0e4c1568bfdb09

Inspect core/huddle.go at lines 417-420 and the surrounding context at commit 985f9a2814e08077b7ee113eae0e4c1568bfdb09. Determine whether the range-loop reference creates the reported issue, then classify it as Bug, Mitigated, or Desirable Behavior using the linked classification guidance and leave the corresponding reaction.

Written by the indexing model from the issue text.