github-vet / github-vet/rangeloop-pointer-findings
carlpett/openstack-ceilometer_exporter: main.go; 3 LoC
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- PR metrics pending
Description
Found a possible issue in [carlpett/openstack-ceilometer_exporter](https://www.github.com/carlpett/openstack-ceilometer_exporter) at [main.go](https://github.com/carlpett/openstack-ceilometer_exporter/blob/ac709ac4579c9c071c68a860d7b8cf3325ca9d4e/main.go#L351-L353)
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/carlpett/openstack-ceilometer_exporter/blob/ac709ac4579c9c071c68a860d7b8cf3325ca9d4e/main.go#L351-L353)
Click here to show the 3 line(s) of Go which triggered the analyzer.
```go
for _, sample := range data {
ch <- sampleToMetric(&sample, metric)
}
```
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 {sampleToMetric 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: ac709ac4579c9c071c68a860d7b8cf3325ca9d4e
Contributor guide
No contributing guide indexed for this repository
Research direction
Read main.go around lines 351-353 and inspect sampleToMetric plus the linked commit context. Determine whether taking &sample in the range loop affects the downstream call, then record the applicable Bug, Mitigated, or Desirable Behavior classification requested by the issue; no test or patch target is named.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100