me
/
glitchier-soc
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cfe91ac984'
${ noResults }
glitchier-soc/app/workers/after_remote_follow_worker.rb

18 lines
451 B
Raw Normal View History Unescape

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
8 years ago
# 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.
8 years ago
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
8 years ago
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
8 years ago
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
8 years ago
follow.destroy
FollowService.new.call(follow.account, updated_account.acct)
end
end