glitchier-soc/app/workers/after_remote_follow_worker.rb

# frozen_string_literal: true

class AfterRemoteFollowWorker
  include Sidekiq::Worker

  sidekiq_options queue: 'pull', retry: 5

  def perform(follow_id)
    follow          = Follow.find(follow_id)
    updated_account = FetchRemoteAccountService.new.call(follow.target_account.remote_url)

    return if updated_account.nil? || !updated_account.locked?

    follow.destroy
    FollowService.new.call(follow.account, updated_account.acct)
  end
end
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 15:12:29 +02: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-04 01:53:20 +03: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 15:12:29 +02: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 18:28:15 +02: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 15:12:29 +02:00
			`follow.destroy`
			`FollowService.new.call(follow.account, updated_account.acct)`
			`end`
			`end`