ppegusii/cs677-smart-homes-IoT: gateway/gateway.go; 9 LoC

Found a possible issue in [ppegusii/cs677-smart-homes-IoT](https://www.github.com/ppegusii/cs677-smart-homes-IoT) at [gateway/gateway.go](https://github.com/ppegusii/cs677-smart-homes-IoT/blob/eba77ff6ba05dfe01ac8f6e926eb146535376bc1/gateway/gateway.go#L90-L98)

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.](https://github.com/ppegusii/cs677-smart-homes-IoT/blob/eba77ff6ba05dfe01ac8f6e926eb146535376bc1/gateway/gateway.go#L90-L98)

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

```go
for tempId, regParams := range tempIdRegParams {
//Query temperature sensor
g.rpcSync.RpcSync(regParams.Address, regParams.Port,
"TemperatureSensor.QueryState",
&tempId, &tempReply, false)
log.Printf("Received temp: %d", tempReply.State)
//Write temperature sensor state to database
g.writeStateInfo("Database.AddState", &tempReply)
}

```

Click here to show extra information the analyzer produced.

```
No path was found through the callgraph that could lead to a function which writes a pointer argument.

No path was found through the callgraph that could lead to a function which passes a pointer to third-party code.

root signature {RpcSync 6} was not found in the callgraph; reference was passed directly to third-party code
```

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: eba77ff6ba05dfe01ac8f6e926eb146535376bc1

Read gateway/gateway.go around lines 90-98 and the linked commit context. Inspect the range loop, RpcSync call, and subsequent writeStateInfo call to determine whether the analyzer report represents a real bug, a mitigated case, or desirable behavior. Done means leaving the issue reaction that matches the finding.

Written by the indexing model from the issue text.