github-vet / github-vet/rangeloop-pointer-findings

ezBastion/ezb_db: setup/setup.go; 13 LoC

Open
#15,962 0 comments 0 reactions 0 assignees View on GitHub
fresh small
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
PR metrics pending

Description

Found a possible issue in [ezBastion/ezb_db](https://www.github.com/ezBastion/ezb_db) at [setup/setup.go](https://github.com/ezBastion/ezb_db/blob/35160a2fbbb1687e26f2922d24509d83281e7e7d/setup/setup.go#L461-L473)

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/ezBastion/ezb_db/blob/35160a2fbbb1687e26f2922d24509d83281e7e7d/setup/setup.go#L461-L473)

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

```go
for _, a := range access {
fmt.Print(".")
if db.NewRecord(&a) {
fmt.Println(a, "not found")
if err := db.Create(&a).Error; err != nil {
panic(err)
}
} else {
if err := db.Save(&a).Error; err != nil {
panic(err)
}
}
}

```

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 {NewRecord 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: 35160a2fbbb1687e26f2922d24509d83281e7e7d

Contributor guide

No contributing guide indexed for this repository

Research direction

The finding points to setup/setup.go lines 461-473 in ezBastion/ezb_db; start by reading that loop and checking how the range variable is passed to NewRecord, Create, and Save. Confirm whether the analyzer finding is reproducible and whether relevant tests cover this setup path; done means a clear Bug, Mitigated, or Desirable Behavior classification with any needed regression coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
database
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.