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

itsprinkle/old_ent_crawler: old_ent_/gsxt/creditd/v1.go; 5 LoC

Open
#16,052 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 [itsprinkle/old_ent_crawler](https://www.github.com/itsprinkle/old_ent_crawler) at [old_ent_/gsxt/creditd/v1.go](https://github.com/itsprinkle/old_ent_crawler/blob/41b6169f2de7d11f9fc52e9cb9cf52b44d305ae1/old_ent_/gsxt/creditd/v1.go#L377-L381)

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/itsprinkle/old_ent_crawler/blob/41b6169f2de7d11f9fc52e9cb9cf52b44d305ae1/old_ent_/gsxt/creditd/v1.go#L377-L381)

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

```go
for _, ple2 := range infoV2.Business.Pledges {
var ple EquityPledgeInfo
s2s(&ple2, &ple, nil)
infoV1.Business.EquityPledgeInfos = append(infoV1.Business.EquityPledgeInfos, ple)
}

```

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 {s2s 3} 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: 41b6169f2de7d11f9fc52e9cb9cf52b44d305ae1

Contributor guide

No contributing guide indexed for this repository

Research direction

Read old_ent_/gsxt/creditd/v1.go around lines 377-381, then inspect the surrounding data types and the s2s call mentioned by the analyzer. Decide whether the reported range-loop pointer behavior is a Bug, Mitigated, or Desirable Behavior, and leave the corresponding reaction on the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Bug
Difficulty
2/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.