monorail
/
mastodon
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
mastodon/app/workers/after_remote_follow_worker.rb

20 lines
498 B
Ruby
Raw Normal View History

After FollowService, re-fetch remote account asynchronously, do nothing if account lock info was up to date, otherwise re-do the FollowService with now updated information
2017-02-11 13:12:29 +00:00
# frozen_string_literal: true
class AfterRemoteFollowWorker
include Sidekiq::Worker
Separate background jobs into different queues. ATTENTION: new queue "pull" must be added to the Sidekiq invokation in your systemd file The pull queue will handle link crawling, thread resolving, and OStatus processing. Such tasks are more likely to hang for a longer time (due to network requests) so it is more sensible to not make the "in-house" tasks wait for them.
2017-04-03 22:53:20 +00:00
sidekiq_options queue: 'pull', retry: 5
After FollowService, re-fetch remote account asynchronously, do nothing if account lock info was up to date, otherwise re-do the FollowService with now updated information
2017-02-11 13:12:29 +00:00
def perform(follow_id)
follow = Follow.find(follow_id)
updated_account = FetchRemoteAccountService.new.call(follow.target_account.remote_url)
Adding more unit tests. Fixing Salmon slaps XML
2017-02-12 16:28:15 +00:00
return if updated_account.nil? || !updated_account.locked?
After FollowService, re-fetch remote account asynchronously, do nothing if account lock info was up to date, otherwise re-do the FollowService with now updated information
2017-02-11 13:12:29 +00:00
follow.destroy
FollowService.new.call(follow.account, updated_account.acct)
Only render public payload once in FanOutOnWrite
2017-04-05 12:26:17 +00:00
rescue ActiveRecord::RecordNotFound
true
After FollowService, re-fetch remote account asynchronously, do nothing if account lock info was up to date, otherwise re-do the FollowService with now updated information
2017-02-11 13:12:29 +00:00
end
end