github-vet / github-vet/rangeloop-pointer-findings
lianghucheng/ddz-match: game/session/session.go; 5 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [lianghucheng/ddz-match](https://www.github.com/lianghucheng/ddz-match) at [game/session/session.go](https://github.com/lianghucheng/ddz-match/blob/caa8d8cfc930fbd1c9d202ed70ba6b6ebb1ae775/game/session/session.go#L709-L713)
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/lianghucheng/ddz-match/blob/caa8d8cfc930fbd1c9d202ed70ba6b6ebb1ae775/game/session/session.go#L709-L713)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for _, v := range *backFlowdatas {
v.FlowIDs = append(v.FlowIDs, fid)
v.ChangeAmount += utils.Decimal(awardAmount)
db.SaveFlowdata(&v)
}
```
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 {SaveFlowdata 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: caa8d8cfc930fbd1c9d202ed70ba6b6ebb1ae775
Contributor guide
No contributing guide indexed for this repository
Research direction
Open game/session/session.go at lines 709-713 and read the surrounding loop and SaveFlowdata call. Determine whether the range variable handling is a bug, mitigated, or desirable behavior, then leave the corresponding reaction described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, game-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100