technoweenie/coffee-resque issues and pull requests

#48 - Having several local workers work on the same queue

Issue - State: closed - Opened by louisameline over 8 years ago - 3 comments

#47 - Fix redis to 1.0.0

Pull Request - State: closed - Opened by ndrsn about 9 years ago - 1 comment

#46 - How do I handle connection to Redis errors ?

Issue - State: open - Opened by louisameline over 9 years ago - 7 comments

#45 - Defaulting the port & host to resolve an incompatibility issue with node-...

Pull Request - State: closed - Opened by steelThread over 9 years ago

#44 - node-redis >= 0.12. incompatibility

Issue - State: open - Opened by steelThread over 9 years ago - 1 comment

#43 - enqueue without a function inserts "undefined" into the queue

Pull Request - State: closed - Opened by Sailias over 9 years ago - 9 comments

#42 - added size method to coffee-resque to get number of jobs in queue.

Pull Request - State: closed - Opened by MishaConway over 9 years ago - 3 comments

#41 - Workers not dequeing jobs

Issue - State: closed - Opened by louisameline over 10 years ago - 5 comments

#40 - Resque interoperability between languages

Issue - State: closed - Opened by malisetti over 10 years ago - 3 comments

#39 - blpop would reduce the cpu%

Pull Request - State: closed - Opened by yorkie almost 11 years ago - 2 comments

#38 - Add callback for enqueue()

Pull Request - State: closed - Opened by kcoder666 almost 11 years ago - 12 comments

#37 - High CPU within the `process.title`

Pull Request - State: closed - Opened by yorkie almost 11 years ago - 2 comments

#36 - Replaced version placeholder in README with new version number

Pull Request - State: closed - Opened by jasonbosco over 11 years ago

#35 - Added blurb about the change in worker polling mechanism

Pull Request - State: closed - Opened by jasonbosco over 11 years ago - 2 comments

#34 - Fixed worker polling mechanism

Pull Request - State: closed - Opened by jasonbosco over 11 years ago - 6 comments

#33 - Worker polling mechanism different from Ruby resque?

Issue - State: closed - Opened by jasonbosco over 11 years ago - 6 comments

#32 - Worker PID Cleanup on Boot

Issue - State: open - Opened by evantahler over 11 years ago - 2 comments

#31 - Worker.end() does not delete all keys in redis

Pull Request - State: closed - Opened by jasonbosco about 12 years ago - 6 comments

#30 - Passing arguments without array breaks it

Issue - State: closed - Opened by StevePotter about 12 years ago - 3 comments

#29 - This is not a port

Issue - State: closed - Opened by Radagaisus about 12 years ago - 1 comment

#28 - Can we get some more examples?

Issue - State: closed - Opened by mavrick about 12 years ago - 1 comment

#26 - Register working job in redis

Pull Request - State: closed - Opened by gshiftlabs-dbuttineau over 12 years ago - 10 comments

#25 - Resque Web dont display workers well and throws error

Issue - State: closed - Opened by smokeymcpod over 12 years ago - 4 comments

#24 - access queue when: worker.on "poll"

Issue - State: closed - Opened by optikfluffel over 12 years ago - 3 comments

#23 - Fix #17, which allows resque-web to properly display workers

Pull Request - State: closed - Opened by mratzloff over 12 years ago - 3 comments

#22 - processing pauses on first empty queue

Issue - State: closed - Opened by kcburge over 12 years ago - 6 comments

#21 - Emitting "error" on connection failure

Issue - State: closed - Opened by gtracy over 12 years ago - 6 comments

#20 - Use error properties to give proper information

Pull Request - State: closed - Opened by devdazed over 12 years ago

#19 - process.title

Issue - State: closed - Opened by AurelienGasser almost 13 years ago - 7 comments

#18 - 'job' event, running async code

Issue - State: closed - Opened by balgarath almost 13 years ago - 3 comments

#17 - Resque-web workers list

Issue - State: closed - Opened by JonathanKnight about 13 years ago - 1 comment

#16 - Why not to use blocking redis operators insted of pooling?

Issue - State: closed - Opened by lexer about 13 years ago - 3 comments

#15 - not parsing args correctly when running jobs?

Issue - State: closed - Opened by cmeiklejohn about 13 years ago - 10 comments

#14 - Added GFM syntax highlighting to code blocks. Also tweaked some bits of

Pull Request - State: closed - Opened by Zearin about 13 years ago - 1 comment

#13 - Polling for jobs just stops when idled for extended period

Issue - State: closed - Opened by perezd over 13 years ago - 4 comments

#12 - Added ability to use a redis password with Coffee Resque

Pull Request - State: closed - Opened by perezd over 13 years ago - 6 comments

#11 - Failure error object?

Issue - State: closed - Opened by kainosnoema over 13 years ago - 14 comments

#10 - No ./lib in npm release?

Issue - State: closed - Opened by kainosnoema over 13 years ago - 6 comments

#9 - Workers stop polling mysteriously

Issue - State: closed - Opened by liangzan over 13 years ago - 3 comments

#8 - readme mistake

Issue - State: closed - Opened by liangzan over 13 years ago - 1 comment

#7 - npm release 0.1.0 broken

Issue - State: closed - Opened by jharlap over 13 years ago - 4 comments

#6 - Callback Notification

Pull Request - State: closed - Opened by steelThread almost 14 years ago - 2 comments

#5 - polling algorithm is so wrong

Issue - State: closed - Opened by technoweenie almost 14 years ago - 2 comments

#4 - Jobs with non blocking behaviors

Issue - State: closed - Opened by steelThread almost 14 years ago - 5 comments

#3 - Easier install process

Pull Request - State: closed - Opened by chetan51 almost 14 years ago - 3 comments

#2 - Using pub / sub instead of polling

Issue - State: closed - Opened by chetan51 almost 14 years ago - 3 comments

#1 - no events emitted while job is running

Issue - State: closed - Opened by frank06 almost 14 years ago - 1 comment

GitHub / technoweenie/coffee-resque issues and pull requests