github-vet / github-vet/rangeloop-pointer-findings
odysa/job-hunter: fetch/fetch.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [odysa/job-hunter](https://www.github.com/odysa/job-hunter) at [fetch/fetch.go](https://github.com/odysa/job-hunter/blob/058cc27b7d40c3429e73a6b74f6c02171c19892c/fetch/fetch.go#L26-L28)
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/odysa/job-hunter/blob/058cc27b7d40c3429e73a6b74f6c02171c19892c/fetch/fetch.go#L26-L28)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, x := range cookies {
req.AddCookie(&x)
}
```
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 {AddCookie 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: 058cc27b7d40c3429e73a6b74f6c02171c19892c
Contributor guide
No contributing guide indexed for this repository
Research direction
Read fetch/fetch.go lines 26-28 at commit 058cc27b7d40c3429e73a6b74f6c02171c19892c, then review the linked analyzer guidance for range-loop findings. Decide whether the shown AddCookie use 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
- devtools
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100