github-vet / github-vet/rangeloop-pointer-findings
frysztak/niebieskie-tramwaje-backend: News/database.go; 6 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [frysztak/niebieskie-tramwaje-backend](https://www.github.com/frysztak/niebieskie-tramwaje-backend) at [News/database.go](https://github.com/frysztak/niebieskie-tramwaje-backend/blob/b73920f2020cca78c09aac95d44268330eaf19d4/News/database.go#L46-L51)
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/frysztak/niebieskie-tramwaje-backend/blob/b73920f2020cca78c09aac95d44268330eaf19d4/News/database.go#L46-L51)
Click here to show the 6 line(s) of Go which triggered the analyzer.
```go
for _, newsItem := range news {
tx.NamedExec(`
INSERT OR IGNORE INTO news (url, title, published_on, synopsis, affects_lines, affects_days, body)
VALUES (:url, :title, :published_on, :synopsis, :affects_lines, :affects_days, :body)`,
&newsItem)
}
```
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 {NamedExec 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: b73920f2020cca78c09aac95d44268330eaf19d4
Contributor guide
No contributing guide indexed for this repository
Research direction
Read News/database.go at lines 46-51 and inspect the range loop, the NamedExec call, and the analyzer details. Determine whether this finding is a Bug, Mitigated, or Desirable Behavior, then leave the corresponding reaction on the issue; completion is the classification reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100