gitlab-ce/app/models/concerns/after_commit_queue.rb

56 lines
1.4 KiB
Ruby

# frozen_string_literal: true
module AfterCommitQueue
extend ActiveSupport::Concern
included do
after_commit :_run_after_commit_queue
after_rollback :_clear_after_commit_queue
end
def run_after_commit(&block)
_after_commit_queue << block if block
true
end
# When within a database transaction, execute the given block after the transaction is committed.
# Otherwise execute the given block
# ATTENTION: because this uses `instance_eval` to evaluate the block, instance variables
# within the block will be evaluated based on the object on which `run_after_commit_or_now` gets executed.
# https://gitlab.com/gitlab-org/gitlab/-/merge_requests/146208#note_1800349073
def run_after_commit_or_now(&block)
if self.class.inside_transaction?
if connection.current_transaction.records&.include?(self)
run_after_commit(&block)
else
# If the current transaction does not include this record, we can run
# the block now, even if it queues a Sidekiq job.
Sidekiq::Worker.skipping_transaction_check do
instance_eval(&block)
end
end
else
instance_eval(&block)
end
true
end
protected
def _run_after_commit_queue
while action = _after_commit_queue.pop
self.instance_eval(&action)
end
end
def _after_commit_queue
@after_commit_queue ||= []
end
def _clear_after_commit_queue
_after_commit_queue.clear
end
end