You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I'm running some tests with ActiveJob, Rspec, Parallel and Sidekiq of course, putting jobs inside Parallel with any in_processes value than 0, makes jobs not to queue, but as I said, if I set in_processes = 0, all jobs are inqueued. Is this a Parallel's bug?
The text was updated successfully, but these errors were encountered:
I'd assume they get queued in a separate thread that then gets killed ... need to configure the backend to be something persistent like redis for thisto work, or use in_threads: X
if it uses redis then that should work
reproduce by doing fork { enqueue } and if that does not work then open an issue with sidekiq
basically I don't think parallel is at faul since it just forks so bug must be somewhere else
... might be something like that the enqueue does not directly write to redis but gets sent into some background thread and then that thread is killed, but no idea
Hi, I'm running some tests with ActiveJob, Rspec, Parallel and Sidekiq of course, putting jobs inside Parallel with any in_processes value than 0, makes jobs not to queue, but as I said, if I set in_processes = 0, all jobs are inqueued. Is this a Parallel's bug?
The text was updated successfully, but these errors were encountered: