github-vet / github-vet/rangeloop-pointer-findings
nntaoli-project/goex: huobi/Hbdm_Ws.go; 4 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [nntaoli-project/goex](https://www.github.com/nntaoli-project/goex) at [huobi/Hbdm_Ws.go](https://github.com/nntaoli-project/goex/blob/40a38c26ac4d60265d65b59c3cac5a8ebbf3222d/huobi/Hbdm_Ws.go#L190-L193)
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/nntaoli-project/goex/blob/40a38c26ac4d60265d65b59c3cac5a8ebbf3222d/huobi/Hbdm_Ws.go#L190-L193)
Click here to show the 4 line(s) of Go which triggered the analyzer.
```go
for _, v := range trades {
v.Pair = pair
hbdmWs.tradeCallback(&v, contract)
}
```
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 {tradeCallback 2} 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: 40a38c26ac4d60265d65b59c3cac5a8ebbf3222d
Contributor guide
No contributing guide indexed for this repository
Research direction
Review huobi/Hbdm_Ws.go lines 190-193 and trace the tradeCallback call to assess the analyzer's range-loop finding. Compare the behavior with the linked classification guidance; done means leaving the appropriate Bug, Mitigated, or Desirable Behavior reaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100