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

AlanLi000/hyperledger: fabric/core/committer/txvalidator/validator.go; 18 LoC

Open
#8,781 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 [AlanLi000/hyperledger](https://www.github.com/AlanLi000/hyperledger) at [fabric/core/committer/txvalidator/validator.go](https://github.com/AlanLi000/hyperledger/blob/726fa71b42b412d1e83adb78ebe68f1ec972beca/fabric/core/committer/txvalidator/validator.go#L178-L195)

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.

> range-loop variable d used in defer or goroutine at line 189

[Click here to see the code in its original context.](https://github.com/AlanLi000/hyperledger/blob/726fa71b42b412d1e83adb78ebe68f1ec972beca/fabric/core/committer/txvalidator/validator.go#L178-L195)

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

```go
for tIdx, d := range block.Data.Data {
tIdxLcl := tIdx
dLcl := d

// ensure that we don't have too many concurrent validation workers
v.support.Acquire(context.Background(), 1)

go func() {
defer v.support.Release(1)

validateTx(&blockValidationRequest{
d: dLcl,
block: block,
tIdx: tIdxLcl,
v: v,
}, results)
}()
}

```

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: 726fa71b42b412d1e83adb78ebe68f1ec972beca

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.