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

richarddennis/btc_crawler_go: crawler.go; 22 LoC

Open
#9,610 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 [richarddennis/btc_crawler_go](https://www.github.com/richarddennis/btc_crawler_go) at [crawler.go](https://github.com/richarddennis/btc_crawler_go/blob/2cff79b5366c13b60a4fa0ee64196c4508ad76c1/crawler.go#L177-L198)

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 address used in defer or goroutine at line 187

[Click here to see the code in its original context.](https://github.com/richarddennis/btc_crawler_go/blob/2cff79b5366c13b60a4fa0ee64196c4508ad76c1/crawler.go#L177-L198)

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

```go
for address := range c.queue.Iter() {
// Reserve worker slot (block)
workerChan <- struct{}{}

if isDone {
break
}

// Start worker
go func() {
r := c.handleAddress(address)

// Process the result
if c.process(r) != nil {
result <- *r
}

// Clear worker slot
<-workerChan
c.waitGroup.Done()
}()
}

```

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: 2cff79b5366c13b60a4fa0ee64196c4508ad76c1

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.