technoweenie / coffee-resque

technoweenie/coffee-resque Issues

process.title
Closed a year ago7
Can we get some more examples?
Closed 3 years ago1
Having several local workers work on the same queue
Closed 8 years ago3
How do I handle connection to Redis errors ?
Updated 9 years ago7
node-redis >= 0.12. incompatibility
Updated 9 years ago1
Workers not dequeing jobs
Closed 10 years ago5
Resque interoperability between languages
Closed 10 years ago3
Worker PID Cleanup on Boot
Updated 10 years ago2
processing pauses on first empty queue
Closed 11 years ago6
Worker polling mechanism different from Ruby resque?
Closed 11 years ago6
Passing arguments without array breaks it
Closed 12 years ago3
This is not a port
Closed 12 years ago1
Resque Web dont display workers well and throws error
Closed 12 years ago4
access queue when: worker.on "poll"
Closed 12 years ago3
Resque-web workers list
Closed 12 years ago1
Emitting "error" on connection failure
Closed 12 years ago6
Why not to use blocking redis operators insted of pooling?
Closed 12 years ago3
'job' event, running async code
Closed 12 years ago3
No ./lib in npm release?
Closed 13 years ago6
Failure error object?
Closed 13 years ago14
not parsing args correctly when running jobs?
Closed 13 years ago10
Polling for jobs just stops when idled for extended period
Closed 13 years ago4
polling algorithm is so wrong
Closed 13 years ago2
Using pub / sub instead of polling
Closed 13 years ago3
no events emitted while job is running
Closed 13 years ago1
Workers stop polling mysteriously
Closed 13 years ago3
readme mistake
Closed 13 years ago1
npm release 0.1.0 broken
Closed 13 years ago4
Jobs with non blocking behaviors
Closed 13 years ago5