Alex Ghiculescu 639dab59dc Active Job: `async` adapter should always run jobs immediately if `immediate` set ... This is an internal fix, not user facing. I noticed it while working on https://github.com/rails/rails/pull/48585. The `async` adapter has an `immediate` option, which should only be used in tests. This option should tell the adapter to run jobs inline. This works correctly with `perform_later`, but it does not work with `enqueue_at`, which is what other internal mechanisms such as `retry_job` use. This PR fixes this bug.		2023-07-03 09:02:51 +10:00
..
backburner	[Active Job] `rubocop -a --only Layout/EmptyLineAfterMagicComment`	2017-07-11 13:12:32 +09:00
delayed_job/delayed	Fix warning: method redefined	2020-03-13 18:19:14 +01:00
integration	Active Job: `async` adapter should always run jobs immediately if `immediate` set	2023-07-03 09:02:51 +10:00
queue_classic	Given method here (e.g. perform) should be public_sendable	2020-10-07 20:55:59 +09:00
sneakers	Fix Ruby warnings tickled by the test suite	2018-06-30 10:20:45 +02:00
stubs	Permit ActionController::Parameters for serializable Hash	2018-11-19 17:38:29 -05:00
job_buffer.rb	Clear JobBuffer on teardown	2022-07-18 23:33:07 -04:00