github-vet / github-vet/rangeloop-pointer-findings
fesiong/cobweb: spider.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [fesiong/cobweb](https://www.github.com/fesiong/cobweb) at [spider.go](https://github.com/fesiong/cobweb/blob/dcdf3129fd7b4c1a6e0c127ed898792a9cd0b2ff/spider.go#L251-L253)
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/fesiong/cobweb/blob/dcdf3129fd7b4c1a6e0c127ed898792a9cd0b2ff/spider.go#L251-L253)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, website := range websites {
DB.Where("`domain` = ?", website.Domain).FirstOrCreate(&website)
}
```
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 {FirstOrCreate 1} 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: dcdf3129fd7b4c1a6e0c127ed898792a9cd0b2ff
Contributor guide
No contributing guide indexed for this repository
Research direction
Read spider.go lines 251-253 and the linked code context first. Then review the range-loop finding descriptions in the linked repository and leave a reaction classifying the instance as Bug, Mitigated, or Desirable Behavior; completion is the appropriate reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100