demarches-normaliennes/app/models/concerns/blob_virus_scanner_concern.rb

module BlobVirusScannerConcern
  extend ActiveSupport::Concern

  included do
    before_create :set_pending
  end

  def virus_scanner
    ActiveStorage::VirusScanner.new(self)
  end

  def scan_for_virus_later
    VirusScannerJob.perform_later(self)
  end

  private

  def set_pending
    metadata[:virus_scan_result] ||= ActiveStorage::VirusScanner::PENDING
  end
end
ActiveStorage url should expire after an hour 2019-11-20 16:03:40 +01:00			`module BlobVirusScannerConcern`
Use active storage load hook to extend blob 2019-05-16 18:59:34 +02:00			`extend ActiveSupport::Concern`

			`included do`
			`before_create :set_pending`
			`end`

			`def virus_scanner`
			`ActiveStorage::VirusScanner.new(self)`
			`end`

active_storage: refactor concerns Follow-up of #5953. Refactor the concerns with two goals: - Getting closer from the way ActiveStorage adds its own hooks. Usually ActiveStorage does this using an `Attachment#after_create` hook, which then delegates to the blob to enqueue the job. - Enqueuing each job only once. By hooking on `Attachment#after_create`, we guarantee each job will be added only once. We then let the jobs themselves check if they are relevant or not, and retry or discard themselves if necessary. We also need to update the tests a bit, because Rails' `perform_enqueued_jobs(&block)` test helper doesn't honor the `retry_on` clause of jobs. Instead it forwards the exception to the caller – which makes the test fail. Instead we use the inline version of `perform_enqueued_jobs()`, without a block, which properly ignores errors catched by retry_on. 2021-03-11 14:42:57 +01:00			`def scan_for_virus_later`
			`VirusScannerJob.perform_later(self)`
			`end`

Use active storage load hook to extend blob 2019-05-16 18:59:34 +02:00			`private`

			`def set_pending`
active_storage: refactor concerns Follow-up of #5953. Refactor the concerns with two goals: - Getting closer from the way ActiveStorage adds its own hooks. Usually ActiveStorage does this using an `Attachment#after_create` hook, which then delegates to the blob to enqueue the job. - Enqueuing each job only once. By hooking on `Attachment#after_create`, we guarantee each job will be added only once. We then let the jobs themselves check if they are relevant or not, and retry or discard themselves if necessary. We also need to update the tests a bit, because Rails' `perform_enqueued_jobs(&block)` test helper doesn't honor the `retry_on` clause of jobs. Instead it forwards the exception to the caller – which makes the test fail. Instead we use the inline version of `perform_enqueued_jobs()`, without a block, which properly ignores errors catched by retry_on. 2021-03-11 14:42:57 +01:00			`metadata[:virus_scan_result] \|\|= ActiveStorage::VirusScanner::PENDING`
Use active storage load hook to extend blob 2019-05-16 18:59:34 +02:00			`end`
			`end`