Tim Jones

This is a challenging one that I'm still thinking through. You may want to avoid using singleton and stately queues with singleton keys for now.

This would have the side effect of losing "queue semantics" in my opinion. If a job is active and you want to queue another one once it's done, users wouldn't...

I've added some updates to the linked issue at the top of the thread, #535. I think I'm at a place where I could stop work and push v11. There...

First of all, I'm very appreciative of your time and effort on this. I'm still reviewing, but I wanted to add a couple of quick observations for thought and discussion....

After more thought, I don't think mutating expiration is the right way to handle this. Since we're still going to require a maximum time, expiration seems like the most natural...

Yes, missing heartbeats would trigger a fail/retry to another worker. And, the heartbeat interval would need to be lower, like 30-60s max, not derived from the expiration/max time

I evaluated another framework only once in the 10 years that this project has been alive, so I would assume there are far more alternatives to consider than mocha these...

> @timgit personally I am a big fan of vitest, it has great DX Sounds good to me > current setup doesn't work well with IDEs. What do you mean...

Ah, Webstorm. Is this because mocha doesn't support typescript yet? Regardless, I'm not married to Mocha, so I'm interested in any benefits vitest can provide, having the benefit of being...

> Readme mentions "Queue storage policies to support a variety of rate limiting, debouncing, and concurrency use cases", but I couldn't find any details on supported concurrency management options in...