github-vet / github-vet/rangeloop-pointer-findings
caTUstrophy/backend: endpoints-regions.go; 4 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [caTUstrophy/backend](https://www.github.com/caTUstrophy/backend) at [endpoints-regions.go](https://github.com/caTUstrophy/backend/blob/0ca9a5c5a1829a775b83296e34332b504be10bc2/endpoints-regions.go#L627-L630)
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/caTUstrophy/backend/blob/0ca9a5c5a1829a775b83296e34332b504be10bc2/endpoints-regions.go#L627-L630)
Click here to show the 4 line(s) of Go which triggered the analyzer.
```go
for i, rec := range recommendations {
app.DB.Model(&rec).Preload("Tags").Related(&recommendations[i].Offer)
app.DB.Model(&rec).Preload("Tags").Related(&recommendations[i].Request)
}
```
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 {Model 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: 0ca9a5c5a1829a775b83296e34332b504be10bc2
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with endpoints-regions.go at lines 627-630 and inspect how recommendations and the related database calls are used. Determine whether the analyzer finding represents a bug, mitigated behavior, or desirable behavior, then classify the issue with the requested reaction; done means the finding has a justified classification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100