devfeel/rockman: rpc/handler/handler.go; 6 LoC

Found a possible issue in [devfeel/rockman](https://www.github.com/devfeel/rockman) at [rpc/handler/handler.go](https://github.com/devfeel/rockman/blob/25da3ccfc0b6eca328af74b523834583ba2ce6b7/rpc/handler/handler.go#L69-L74)

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 v was used in a composite literal at line 71

[Click here to see the code in its original context.](https://github.com/devfeel/rockman/blob/25da3ccfc0b6eca328af74b523834583ba2ce6b7/rpc/handler/handler.go#L69-L74)

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

```go
for k, v := range configs {
execInfos[k] = &core.ExecutorInfo{
TaskConfig: &v,
Worker: h.getNode().NodeInfo(),
}
}

```

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: 25da3ccfc0b6eca328af74b523834583ba2ce6b7

Start by reading rpc/handler/handler.go at lines 69-74 and the linked Go range-loop finding. Check whether the reference to v represents a bug, mitigated issue, or desirable behavior in this context. Done means leaving the corresponding classification reaction on the issue.

Written by the indexing model from the issue text.