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

pingcap/tidb-operator: tests/e2e/util/operator/operator.go; 15 LoC

Open
#14,783 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 [pingcap/tidb-operator](https://www.github.com/pingcap/tidb-operator) at [tests/e2e/util/operator/operator.go](https://github.com/pingcap/tidb-operator/blob/7236eaba7d5924f47ae0cd3b0bf928886ca8cfc3/tests/e2e/util/operator/operator.go#L74-L88)

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/pingcap/tidb-operator/blob/7236eaba7d5924f47ae0cd3b0bf928886ca8cfc3/tests/e2e/util/operator/operator.go#L74-L88)

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

```go
for _, pod := range pods {
if !podutil.IsPodReady(&pod) || hasBeenRestarted(&pod) {
// deleting the pod will recreate it, we should skip if the pod
// is not ready or has been restarted before, otherwise
// potential errors (e.g. panic) in operator may be hidden.
framework.Logf("pod %s/%s is not ready or crashed before, skip deleting", pod.Namespace, pod.Name)
continue
}
err = k.client.CoreV1().Pods(pod.Namespace).Delete(pod.Name, &metav1.DeleteOptions{})
if err != nil {
framework.Logf("failed to delete pod %s/%s: %v", pod.Namespace, pod.Name, err)
} else {
framework.Logf("successfully deleted pod %s/%s", pod.Namespace, pod.Name)
}
}

```

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 {IsPodReady 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: 7236eaba7d5924f47ae0cd3b0bf928886ca8cfc3

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.