Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / ivpusic/grpool issues and pull requests
#13 - Why do you insert data into the channel and take it out immediately? What's the effect?
Issue -
State: open - Opened by 1325075688gw almost 3 years ago
- 2 comments
#12 - if a pool instance used cross go routine, wg.Add() wg.Done() not work correctly as purpose
Issue -
State: open - Opened by rabbitHX over 3 years ago
#11 - panic: sync: negative WaitGroup counter
Issue -
State: open - Opened by codenoid about 4 years ago
#10 - tagged releases?
Issue -
State: closed - Opened by anarcat over 5 years ago
- 2 comments
#9 - need fixes to run examples/first.go and examples/second.go
Issue -
State: closed - Opened by progamer71 about 6 years ago
- 1 comment
#8 - Add support for future mechanism
Issue -
State: closed - Opened by wanghongfei about 6 years ago
- 2 comments
#7 - Does it support asynchronous mechanisms?
Issue -
State: open - Opened by wpecker over 6 years ago
#6 - Optimize completion signal and add benchmarks
Pull Request -
State: closed - Opened by agnivade about 7 years ago
- 1 comment
#5 - Unsafe loop with loop variable & closure
Issue -
State: closed - Opened by giter over 7 years ago
#4 - Can I send param to workpool?
Issue -
State: closed - Opened by JackTiger about 8 years ago
- 1 comment
#3 - i think it's better to add panic recover for each worker go routine.
Issue -
State: open - Opened by WanliTian over 8 years ago
- 2 comments
#2 - typo(README.md): coustom -> custom
Pull Request -
State: closed - Opened by jlandure about 9 years ago
- 1 comment
#1 - worker should recover potential panic
Pull Request -
State: closed - Opened by weekface about 9 years ago
- 1 comment