technoweenie coffee-resque issues

technoweenie / coffee-resque

MIT License

546 stars 44 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

Having several local workers work on the same queue

#48 louisameline closed 8 years ago
3
Fix redis to 1.0.0

#47 ndrsn closed 4 years ago
1
How do I handle connection to Redis errors ?

#46 louisameline opened 9 years ago
7
Defaulting the port & host to resolve an incompatibility issue with node-...

#45 steelThread closed 9 years ago
0
node-redis >= 0.12. incompatibility

#44 steelThread opened 9 years ago
1
enqueue without a function inserts "undefined" into the queue

#43 Sailias closed 9 years ago
9
added size method to coffee-resque to get number of jobs in queue.

#42 MishaConway closed 9 years ago
3
Workers not dequeing jobs

#41 louisameline closed 10 years ago
5
Resque interoperability between languages

#40 malisetti closed 10 years ago
3
blpop would reduce the cpu%

#39 yorkie closed 10 years ago
2
Add callback for enqueue()

#38 kcoder666 closed 10 years ago
12
High CPU within the `process.title`

#37 yorkie closed 10 years ago
2
Replaced version placeholder in README with new version number

#36 jasonbosco closed 11 years ago
0
Added blurb about the change in worker polling mechanism

#35 jasonbosco closed 11 years ago
2
Fixed worker polling mechanism

#34 jasonbosco closed 11 years ago
6
Worker polling mechanism different from Ruby resque?

#33 jasonbosco closed 11 years ago
6
Worker PID Cleanup on Boot

#32 evantahler opened 11 years ago
2
Worker.end() does not delete all keys in redis

#31 jasonbosco closed 12 years ago
6
Passing arguments without array breaks it

#30 StevePotter closed 12 years ago
3
This is not a port

#29 Radagaisus closed 12 years ago
1
Can we get some more examples?

#28 mavrick closed 3 years ago
1
Register working job in redis

#26 gshiftlabs-dbuttineau closed 12 years ago
10
Resque Web dont display workers well and throws error

#25 smokeymcpod closed 12 years ago
4
access queue when: worker.on "poll"

#24 optikfluffel closed 12 years ago
3
Fix #17, which allows resque-web to properly display workers

#23 mratzloff closed 12 years ago
3
processing pauses on first empty queue

#22 kcburge closed 11 years ago
6
Emitting "error" on connection failure

#21 gtracy closed 12 years ago
6
Use error properties to give proper information

#20 devdazed closed 12 years ago
0
process.title

#19 AurelienGasser closed 1 year ago
7
'job' event, running async code

#18 balgarath closed 12 years ago
3
Resque-web workers list

#17 JonathanKnight closed 12 years ago
1
Why not to use blocking redis operators insted of pooling?

#16 lexer closed 12 years ago
3
not parsing args correctly when running jobs?

#15 cmeiklejohn closed 13 years ago
10
Added GFM syntax highlighting to code blocks. Also tweaked some bits of

#14 Zearin closed 13 years ago
1
Polling for jobs just stops when idled for extended period

#13 perezd closed 13 years ago
4
Added ability to use a redis password with Coffee Resque

#12 perezd closed 13 years ago
6
Failure error object?

#11 kainosnoema closed 13 years ago
14
No ./lib in npm release?

#10 kainosnoema closed 13 years ago
6
Workers stop polling mysteriously

#9 liangzan closed 13 years ago
3
readme mistake

#8 liangzan closed 13 years ago
1
npm release 0.1.0 broken

#7 jharlap closed 13 years ago
4
Callback Notification

#6 steelThread closed 13 years ago
2
polling algorithm is so wrong

#5 technoweenie closed 13 years ago
2
Jobs with non blocking behaviors

#4 steelThread closed 13 years ago
5
Easier install process

#3 chetan51 closed 13 years ago
3
Using pub / sub instead of polling

#2 chetan51 closed 13 years ago
3
no events emitted while job is running

#1 frank06 closed 13 years ago
1