abcdabcd987/SubmitBest: web/app/controllers/app.go; 4 LoC

Found a possible issue in [abcdabcd987/SubmitBest](https://www.github.com/abcdabcd987/SubmitBest) at [web/app/controllers/app.go](https://github.com/abcdabcd987/SubmitBest/blob/ebb9beecad05d3d0fbdf4c622adf8e3621a2b0be/web/app/controllers/app.go#L761-L764)

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 p is reassigned at line 762

[Click here to see the code in its original context.](https://github.com/abcdabcd987/SubmitBest/blob/ebb9beecad05d3d0fbdf4c622adf8e3621a2b0be/web/app/controllers/app.go#L761-L764)

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

```go
for _, p := range problems {
problemMap[p.ShortName] = &p
problemNames = append(problemNames, p.ShortName)
}

```

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

Read web/app/controllers/app.go around lines 761-764 and inspect the linked commit context to understand how problemMap is used. Confirm whether the analyzer finding represents a bug, mitigation, or desirable behavior, then leave the corresponding reaction on the issue; completion is the selected classification.

Written by the indexing model from the issue text.