github-vet / github-vet/rangeloop-pointer-findings
Ahmadposten/DC-OS-autoscaling: dcos-autoscaling.go; 12 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [Ahmadposten/DC-OS-autoscaling](https://www.github.com/Ahmadposten/DC-OS-autoscaling) at [dcos-autoscaling.go](https://github.com/Ahmadposten/DC-OS-autoscaling/blob/b566a1230d5d20d5605d582067f6fa6a7cc66b75/dcos-autoscaling.go#L22-L33)
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 application used in defer or goroutine at line 24
[Click here to see the code in its original context.](https://github.com/Ahmadposten/DC-OS-autoscaling/blob/b566a1230d5d20d5605d582067f6fa6a7cc66b75/dcos-autoscaling.go#L22-L33)
Click here to show the 12 line(s) of Go which triggered the analyzer.
```go
for k, application := range managedApplications {
go func(wg *sync.WaitGroup) {
application.SyncRules()
application.GetStatistics()
application.CalibrateDesired()
if application.Instances != application.Desired {
application.Adapt()
}
managedApplications[k] = application
wg.Done()
}(&wg)
}
```
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: b566a1230d5d20d5605d582067f6fa6a7cc66b75
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.