github-vet / github-vet/rangeloop-pointer-findings
gentoo/soko: pkg/portage/projects/update.go; 10 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [gentoo/soko](https://www.github.com/gentoo/soko) at [pkg/portage/projects/update.go](https://github.com/gentoo/soko/blob/bf33f10b9eb13d07346f1a79ae0695d4f6beb0ed/pkg/portage/projects/update.go#L35-L44)
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/gentoo/soko/blob/bf33f10b9eb13d07346f1a79ae0695d4f6beb0ed/pkg/portage/projects/update.go#L35-L44)
Click here to show the 10 line(s) of Go which triggered the analyzer.
```go
for _, project := range projectList.Projects {
database.DBCon.Insert(&project)
for _, member := range project.Members {
database.DBCon.Insert(&models.MaintainerToProject{
Id: member.Email + "-" + project.Email,
MaintainerEmail: member.Email,
ProjectEmail: project.Email,
})
}
}
```
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 {Insert 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: bf33f10b9eb13d07346f1a79ae0695d4f6beb0ed
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with pkg/portage/projects/update.go at the referenced commit and inspect the range loop and database.DBCon.Insert calls. Determine whether the reported pointer usage causes incorrect persisted project or maintainer records, then classify the finding as Bug, Mitigated, or Desirable Behavior using the issue reactions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100