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

gonium/her0ld: src/github.com/gonium/her0ld/bots/eventbot.go; 5 LoC

Open
#13,826 0 comments 0 reactions 0 assignees View on GitHub
fresh tiny
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
PR metrics pending

Description

Found a possible issue in [gonium/her0ld](https://www.github.com/gonium/her0ld) at [src/github.com/gonium/her0ld/bots/eventbot.go](https://github.com/gonium/her0ld/blob/6b3d0cde31350b954448908e423c8bd30000fefc/src/github.com/gonium/her0ld/bots/eventbot.go#L374-L378)

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/gonium/her0ld/blob/6b3d0cde31350b954448908e423c8bd30000fefc/src/github.com/gonium/her0ld/bots/eventbot.go#L374-L378)

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

```go
for _, event := range events {
b.Db.Delete(&event)
answer = append(answer, fmt.Sprintf(EVENTBOT_CMD_DELETED_EVENT,
event.Id))
}

```

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 {Delete 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: 6b3d0cde31350b954448908e423c8bd30000fefc

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with src/github.com/gonium/her0ld/bots/eventbot.go around lines 374-378 and inspect the surrounding event deletion flow. Compare that code with the analyzer details and linked original context; done means classifying the finding as Bug, Mitigated, or Desirable Behavior.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.