mrzxy/nineone: spider.go; 17 LoC

Found a possible issue in [mrzxy/nineone](https://www.github.com/mrzxy/nineone) at [spider.go](https://github.com/mrzxy/nineone/blob/a69a068333da57f3e79b228a00c174097201d34e/spider.go#L92-L108)

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/mrzxy/nineone/blob/a69a068333da57f3e79b228a00c174097201d34e/spider.go#L92-L108)

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

```go
for _, v := range res.Data.List {
//tt, _ := time.ParseInLocation("2006-01-02", v.UpTime, loc)
//if tt.Before(zeroT) && !zeroT.Equal(tt) {
if page > *fp {
over = true
break
}
exist := ! db.DB().Select("id").
Where("vid = ?", v.Vid).First(&db.VideoList{}).RecordNotFound()
if exist {
existNo += 1
continue
}
m := db.VideoList{}
CopyStruct(&v, &m)
data = append(data, m)
}

```

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 {CopyStruct 2} 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: a69a068333da57f3e79b228a00c174097201d34e

Read spider.go lines 92-108 and the analyzer details, then inspect the linked project context to understand the reported range-loop finding. Decide whether this instance is a Bug, Mitigated, or Desirable Behavior, and leave the corresponding reaction on the issue; completion is the classification reaction.

Written by the indexing model from the issue text.