Added ability to reset the timeout

[bugs181]

Example use:

q.on('timeout', (next, job, resetTimeout) => {
  if (job.stillAlive) {
    console.log('Job said it was still working on something, giving it more time to finish')
    job.stillAlive = false
    resetTimeout()
    return
  }

  processJobError(job, 'Job timed out')
  next()
})

[jessetane]

Another contributor added this feature recently, does it cover your use case?

321fe6e

[bugs181]

Another contributor added this feature recently, does it cover your use case?

321fe6e

Unfortunately, the linked feature is an opt-out of timeouts. What I needed was a way to extend the timeout based on some event. I still want timeouts just in case the "job" fails to execute or whatever.

As a concrete example, using the job.stillAlive check. In my particular application, stillAlive is set every time new data comes in from a download event handler. We still want timeouts just in case the network is interrupted or some other event happens.

[jessetane]

Well, to be fair, that feature allows you to set custom timeouts per job, not just opt out.

Anyhow your reset idea is cool, but I wonder, should we fix this first?

#66

[bugs181]

should we fix this first?

Oof! Good catch. I'll see if I can implement a PR.