David Verhasselt
David Verhasselt
Since Ruby 2.5 there's the `Warning` module that one can use to customise `Kernel#warn`. The gem `warning` adds some extra utils. We've used it as follows to silence this annoying...
Hey @oelmekki sure thing - I update the original code in the post above.
Makes sense yeah. Should probably be removed from the README then to avoid confusion.
Please change this. I bumped into this seemingly arbitrary limitation on my first commit-sync. I had to go back to CLI and do a manual "git push".
Interesting, good catch! I think we should not allow a single Redis client to be used in different threads like this, because I'm guessing the BLPOP command we're using (which...
@felipeclopes I would suggest using different connections, it should work. Can you give an example where you don't get a lock, with different connections? The deadlock that happens if you...
@felipeclopes if it didn't block when using different connections, then that's a bug in redis-semaphore, since that should definitely work (it's the reason I made it :) ). Could you...
Thanks for reminding me @stephankaag, I'll find some free time this week and work through the open issues on this gem.
I agree, due to the blocking nature of some usecases of `redis-semaphore`, reusing redis clients should be discouraged. Since even adding a Ruby mutex to the blocking code in redis-semaphore...
Hey @mediaslave24 thanks for contributing. However I found some problems with your code. Could you go through my comments and update, then I'll merge. Thanks!