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

mumoshu/variant: pkg/sandbox/task.go; 15 LoC

Open
#14,081 0 comments 0 reactions 0 assignees View on GitHub
fresh small
Dominant language
No language data
Stars
0
Forks
0
PR merge metrics
PR metrics pending

Description

Found a possible issue in [mumoshu/variant](https://www.github.com/mumoshu/variant) at [pkg/sandbox/task.go](https://github.com/mumoshu/variant/blob/2bf0c711c6bc534a86f6cb6bb5712cbc00b73ec7/pkg/sandbox/task.go#L76-L90)

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/mumoshu/variant/blob/2bf0c711c6bc534a86f6cb6bb5712cbc00b73ec7/pkg/sandbox/task.go#L76-L90)

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

```go
for _, next := range f.Tasks {
if next.Name == targetChildName {
if len(components) == 1 {
return current.Push(&next), nil
} else {
rest, err := next.BuildStackUntil(components[1:])

if err != nil {
return nil, err
}

return current.Concat(rest), nil
}
}
}

```

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 {Push 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: 2bf0c711c6bc534a86f6cb6bb5712cbc00b73ec7

Contributor guide

No contributing guide indexed for this repository

Research direction

Read the Go snippet in pkg/sandbox/task.go at lines 76-90 and the linked range-loop finding guidance. Check the surrounding context and classify the analyzer finding by leaving the appropriate reaction: Bug, Mitigated, or Desirable Behavior.

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
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.