github-vet / github-vet/rangeloop-pointer-findings
pantacor/pantahub-base: utils/scopes.go; 5 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [pantacor/pantahub-base](https://www.github.com/pantacor/pantahub-base) at [utils/scopes.go](https://github.com/pantacor/pantahub-base/blob/f56fe3280bd41fb7e67be79777b9cdee9583e4d6/utils/scopes.go#L286-L290)
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/pantacor/pantahub-base/blob/f56fe3280bd41fb7e67be79777b9cdee9583e4d6/utils/scopes.go#L286-L290)
Click here to show the 5 line(s) of Go which triggered the analyzer.
```go
for i, s := range scopes {
if f(&s, i) {
fapps = append(fapps, s)
}
}
```
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 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: f56fe3280bd41fb7e67be79777b9cdee9583e4d6
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with utils/scopes.go at lines 286-290 in commit f56fe3280bd41fb7e67be79777b9cdee9583e4d6, then trace the callback f and its callers. Determine whether the analyzer finding represents a Bug, Mitigated case, or Desirable Behavior, and record that classification on the issue.
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