dongjun111111/notes: 工具/downBinlog.go; 14 LoC

Found a possible issue in [dongjun111111/notes](https://www.github.com/dongjun111111/notes) at [工具/downBinlog.go](https://github.com/dongjun111111/notes/blob/4a3f7a1244497f9bacbfb4eb621c5b9db074b569/工具/downBinlog.go#L246-L259)

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 k used in defer or goroutine at line 248

[Click here to see the code in its original context.](https://github.com/dongjun111111/notes/blob/4a3f7a1244497f9bacbfb4eb621c5b9db074b569/工具/downBinlog.go#L246-L259)

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

```go
for k, v := range *dLoads {
go func() {
i := k
//单个下载
name, err := downOne(v, path+"/"+dir, i, record)
if err != nil {
ch <- err
} else {
ch <- nil
*names = append(*names, name)
}
}()
time.Sleep(time.Microsecond)
}

```

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: 4a3f7a1244497f9bacbfb4eb621c5b9db074b569

Read 工具/downBinlog.go at lines 246-259 and compare the goroutine's range-variable use with the analyzer guidance linked in the issue. Leave a reaction marking the finding as Bug, Mitigated, or Desirable Behavior; completion is the selected classification.

Written by the indexing model from the issue text.