mastodon/app/workers/processing_worker.rb

# frozen_string_literal: true

class ProcessingWorker
  include Sidekiq::Worker

  sidekiq_options backtrace: true

  def perform(account_id, body)
    ProcessFeedService.new.call(body, Account.find(account_id), override_timestamps: true)
  end
end
Fix rubocop issues, introduce usage of frozen literal to improve performance 2016-11-15 07:56:29 -08:00			`# frozen_string_literal: true`

Delegate processing of incoming PuSH data to background workers 2016-11-15 06:43:33 -08:00			`class ProcessingWorker`
			`include Sidekiq::Worker`
Add API for retrieving blocked accounts 2016-12-29 11:12:32 -08:00
Move OStatus processing back into default queue 2017-04-04 04:02:49 -07:00			`sidekiq_options backtrace: true`
Delegate processing of incoming PuSH data to background workers 2016-11-15 06:43:33 -08:00
			`def perform(account_id, body)`
Fixes/do not override timestamps (#7336) * Revert "Fixes/do not override timestamps (#7331)" This reverts commit 581a5c9d29ef2a12f46b67a1097a9ad6df1c6953. * Document Snowflake ID corner-case a bit more Snowflake IDs are used for two purposes: making object identifiers harder to guess and ensuring they are in chronological order. For this reason, they are based on the `created_at` attribute of the object. Unfortunately, inserting items with older snowflakes IDs will break the assumption of consumers of the paging APIs that new items will always have a greater identifier than the last seen one. * Add `override_timestamps` virtual attribute to not correlate snowflake ID with created_at 2018-05-03 14:02:46 -07:00			`ProcessFeedService.new.call(body, Account.find(account_id), override_timestamps: true)`
Delegate processing of incoming PuSH data to background workers 2016-11-15 06:43:33 -08:00			`end`
			`end`