b5042e5301
The NotificationService has to do quite a lot of work to calculate the
recipients for an email. Where possible, we should try to avoid doing this in an
HTTP request, because the mail are sent by Sidekiq anyway, so there's no need to
schedule those emails immediately.
This commit creates a generic Sidekiq worker that uses Global ID to serialise
and deserialise its arguments, then forwards them to the NotificationService.
The NotificationService gains an `#async` method, so you can replace:
notification_service.new_issue(issue, current_user)
With:
notification_service.async.new_issue(issue, current_user)
And have everything else work as normal, except that calculating the recipients
will be done by Sidekiq, which will then schedule further Sidekiq jobs to send
each email.
31 lines
1,004 B
Ruby
31 lines
1,004 B
Ruby
module MergeRequests
|
|
class ReopenService < MergeRequests::BaseService
|
|
def execute(merge_request)
|
|
return merge_request unless can?(current_user, :update_merge_request, merge_request)
|
|
|
|
if merge_request.reopen
|
|
create_event(merge_request)
|
|
create_note(merge_request, 'reopened')
|
|
notification_service.async.reopen_mr(merge_request, current_user)
|
|
execute_hooks(merge_request, 'reopen')
|
|
merge_request.reload_diff(current_user)
|
|
merge_request.mark_as_unchecked
|
|
invalidate_cache_counts(merge_request, users: merge_request.assignees)
|
|
merge_request.update_project_counter_caches
|
|
end
|
|
|
|
merge_request
|
|
end
|
|
|
|
private
|
|
|
|
def create_event(merge_request)
|
|
# Making sure MergeRequest::Metrics updates are in sync with
|
|
# Event creation.
|
|
Event.transaction do
|
|
event_service.reopen_mr(merge_request, current_user)
|
|
merge_request_metrics_service(merge_request).reopen
|
|
end
|
|
end
|
|
end
|
|
end
|