Buffer size of zero does not work

[haimgel]

We're using Que with jobs that take a really long time to complete (hours), and would like to set up Que so that each worker process does not lock more than the one job that it's currently processes.

When we set minimum_buffer_size and manimum_buffer_size to zero, the workers do not pick any jobs at all. When we set the buffer size to one, the workers start picking up jobs but then they also pick and lock the next job.

Is there any way to configure Que not to lock any jobs beside the one it is currently processing?

[chanks]

I just pushed a minor fix to master so that --minimum_buffer_size 0 --maximum_buffer_size 0 should still pick up enough jobs to satisfy the workers - try it out and let me know if that solves your problem.

(Also master has started failing sometime in the last 10 months, looks like it's due to changes in Rails. I may or may not find time to fix that soon.)

[haimgel]

Thank you so much for your prompt reply and a fix for this! Much appreciated.
Yes, this solves the problem I had with the buffer of zero.

Also master has started failing sometime in the last 10 months, looks like it's due to changes in Rails.

Could you please elaborate a bit about that? I'm testing Que with Rails 5.2.2 on Ruby 2.6, and I didn't notice any breakage. Even if you don't have time to fix, could you please open a Github issue with the description of the problem? Maybe someone else can fix that (I cannot promise I'll fix that but I'll at least look into that).

[chanks]

Opened issue #236, I'm going to close this one. Thanks for the report!