From e8c8b00e94b2676552bfc9c2a07fa2a2c026ded0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Javi=20Mart=C3=ADn?= Date: Sat, 15 Jul 2023 14:21:51 +0200 Subject: [PATCH] Skip after callbacks if terminated in active job Not sure this configuration option does anything, though, since it's been removed in Rails 7.0 because it was not halting the callbacks. But, if it does nothing, it's the same as disabling it, which is what we were doing until now, so in the end using the Rails 6.1 default value does no harm. --- config/initializers/new_framework_defaults_6_1.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/initializers/new_framework_defaults_6_1.rb b/config/initializers/new_framework_defaults_6_1.rb index 3a4761aea..9e2590862 100644 --- a/config/initializers/new_framework_defaults_6_1.rb +++ b/config/initializers/new_framework_defaults_6_1.rb @@ -17,7 +17,7 @@ Rails.application.config.active_job.retry_jitter = 0.15 # Stop executing `after_enqueue`/`after_perform` callbacks if # `before_enqueue`/`before_perform` respectively halts with `throw :abort`. -# Rails.application.config.active_job.skip_after_callbacks_if_terminated = true +Rails.application.config.active_job.skip_after_callbacks_if_terminated = true # Specify cookies SameSite protection level: either :none, :lax, or :strict. #