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

DQinYuan/tidb-v3.0.0-wrapped: store/tikv/coprocessor.go; 4 LoC

Open
#15,642 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 [DQinYuan/tidb-v3.0.0-wrapped](https://www.github.com/DQinYuan/tidb-v3.0.0-wrapped) at [store/tikv/coprocessor.go](https://github.com/DQinYuan/tidb-v3.0.0-wrapped/blob/fefd913d06659ee2a8bc8414c1bf42cce0d3687c/store/tikv/coprocessor.go#L262-L265)

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/DQinYuan/tidb-v3.0.0-wrapped/blob/fefd913d06659ee2a8bc8414c1bf42cce0d3687c/store/tikv/coprocessor.go#L262-L265)

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

```go
for _, ran := range r.mid {
trace_util_0.Count(_coprocessor_00000, 56)
f(&ran)
}

```

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 {f 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: fefd913d06659ee2a8bc8414c1bf42cce0d3687c

Contributor guide

No contributing guide indexed for this repository

Research direction

Read store/tikv/coprocessor.go around lines 262-265 and inspect the range loop, the call to f(&ran), and the linked analyzer descriptions. Determine whether this instance is a bug, mitigated, or desirable behavior, then record that classification with the corresponding reaction.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.