github-vet / github-vet/rangeloop-pointer-findings
snappysystem/lbase: balancer/default_balancer.go; 4 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [snappysystem/lbase](https://www.github.com/snappysystem/lbase) at [balancer/default_balancer.go](https://github.com/snappysystem/lbase/blob/ce6670aff7be291ce75428c1ed127e55b4e21030/balancer/default_balancer.go#L163-L166)
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/snappysystem/lbase/blob/ce6670aff7be291ce75428c1ed127e55b4e21030/balancer/default_balancer.go#L163-L166)
Click here to show the 4 line(s) of Go which triggered the analyzer.
```go
for r, q := range b.perRackQueue {
heap.Init(&q)
b.perRackQueue[r] = q
}
```
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 {Init 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: ce6670aff7be291ce75428c1ed127e55b4e21030
Contributor guide
No contributing guide indexed for this repository
Research direction
Read balancer/default_balancer.go at lines 163-166 and review the linked rangeclosure-findings classification descriptions. Decide whether the analyzer finding is a Bug, Mitigated, or Desirable Behavior, then record that classification with the corresponding reaction; no test or code change is specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100