Marcelo Lauxen

if you do something like ```yml every: ``` does it work? If you put it just a string it won't be evaluated, it needs to be in `` to be...

@vipulvkp did the suggestion work?

@afrase Are you still interested in working on this?

hey @afrase @FabienChaynes I plan to add this fix to the V4 release, I think we won't be able to merge these changes due to the conflicts. I will open...

@rvyas Did you solved your problem?

@rvyas @mgoggin I didn't take a look at this gem https://github.com/mhenrixon/sidekiq-unique-jobs, but maybe it can help.

ok I think one solution for those problems will be to use a Redis based Lock instead of rufus-scheduler default filelock https://github.com/jmettraux/rufus-scheduler#advanced-lock-schemes This would allow us to use something like...

@bpo Could you exemplify? PS: Only thing we want is to avoid sidekiq-scheduler enqueueing duplicated jobs on multiple hosts

got it @bpo, that makes sense! I agree that adding too much complexity is not a path we want to follow and yeah, what I am looking for is to...

@eldemcan You don't have to patch sidekiq-scheduler, it is just a matter of passing the `scheduler_lock` to the `rufus_scheduler_options`, no? One question, what your team wants is a single scheduler...