technoweenie/coffee-resque

Issues

• process.title

  #19 opened a year ago by AurelienGasser
  7

• Can we get some more examples?

  #28 opened 3 years ago by mavrick
  1

• Having several local workers work on the same queue

  #48 opened 8 years ago by louisameline
  3

• How do I handle connection to Redis errors ?

  #46 opened 9 years ago by louisameline
  7

• node-redis >= 0.12. incompatibility

  #44 opened 10 years ago by steelThread
  1

• Workers not dequeing jobs

  #41 opened 10 years ago by louisameline
  5

• Resque interoperability between languages

  #40 opened 11 years ago by malisetti
  3

• Worker PID Cleanup on Boot

  #32 opened 12 years ago by evantahler
  2

• processing pauses on first empty queue

  #22 opened 11 years ago by kcburge
  6

• Worker polling mechanism different from Ruby resque?

  #33 opened 11 years ago by jasonbosco
  6

• Passing arguments without array breaks it

  #30 opened 12 years ago by StevePotter
  3

• This is not a port

  #29 opened 12 years ago by Radagaisus
  1

• Resque Web dont display workers well and throws error

  #25 opened 12 years ago by smokeymcpod
  4

• access queue when: worker.on "poll"

  #24 opened 12 years ago by optikfluffel
  3

• Resque-web workers list

  #17 opened 12 years ago by JonathanKnight
  1

• Emitting "error" on connection failure

  #21 opened 12 years ago by gtracy
  6

• Why not to use blocking redis operators insted of pooling?

  #16 opened 12 years ago by lexer
  3

• 'job' event, running async code

  #18 opened 13 years ago by balgarath
  3

• No ./lib in npm release?

  #10 opened 13 years ago by kainosnoema
  6

• Failure error object?

  #11 opened 13 years ago by kainosnoema
  14

• not parsing args correctly when running jobs?

  #15 opened 13 years ago by cmeiklejohn
  10

• Polling for jobs just stops when idled for extended period

  #13 opened 13 years ago by perezd
  4

• polling algorithm is so wrong

  #5 opened 13 years ago by technoweenie
  2

• Using pub / sub instead of polling

  #2 opened 13 years ago by chetan51
  3

• no events emitted while job is running

  #1 opened 13 years ago by frank06
  1

• Workers stop polling mysteriously

  #9 opened 13 years ago by liangzan
  3

• readme mistake

  #8 opened 13 years ago by liangzan
  1

• npm release 0.1.0 broken

  #7 opened 14 years ago by jharlap
  4

• Jobs with non blocking behaviors

  #4 opened 14 years ago by steelThread
  5