Anton Sidelnikov

@miaowing Hi! Found that PR. I was looking for similar thing - personally I'm interested in "show info when next run happens" and considered exposing `job.nextInvocation()` from `node-schedule`. I see...

Another solution _could be_ auto-extension from next thread (e.g. you lock with 1 sec, by extend it as you go), so that lock is released fast when locker process dies....

I would be glad to participate implementing both parts if you as an author see it possible 😄

@mike-marcacci Thanks for responding. I've moved away from context where it was used, but I actually would be glad to contribute once I have time 🙂 I really liked your...

@onichandame I'm not sure that infinite retry is safe - since many clients can compete for acquiring a locks (e.g. you get a large burst of concurrent requests for single...

@Menci It's somewhat stale, but still will answer (got interested into topic). TL;DR: - You can't implement safe R/W Lock on top of only Redlock algorithm, since it requires atomic...

@Menci So, if I got it right you use Redlock to lock _counters_ as a resource, so they could be operated atomically 🙂 That's kind smart, yeah! I thought your...

I second request for `testOnly`. Since `NODE_ENV=test` is first-class citizen (there's `isTest`), I think it worth having ability to have different defaults for dev & test will make things more...

Not happy with that as well. Really would like to have better return code without much workarounds 🙂 My workaround was to create custom rejection for this non-interceptable "Not Found"...

@palmerj3 @mattphillips Any chance it can be progressed? Especially since there's POC MR, which kind of really works. Personally also used that behaviour a lot in mocha - to match...