Quieting logs about activejob-uniqueness HOT 3 OPEN

You could pass in a proc that does nothing: https://github.com/veeqo/activejob-uniqueness/blob/main/lib/generators/active_job/uniqueness/templates/config/initializers/active_job_uniqueness.rb#L18

from activejob-uniqueness.

@bmulholland - sorry to not reply earlier. I missed your reply. We actually already tried that. Do you see something I am missing in our syntax?

  unique :until_and_while_executing,
    lock_ttl: 1.hour,
    on_conflict: ->(job) { logger.warn "Already in queue - not queueing again: #{job.arguments}" },
    on_runtime_conflict: ->(job) { logger.warn "Already executing - not queueing again: #{job.arguments}" }

Note that we tried it empty and had no output, and just on a whim moved it to this where we would at least see something if it started running the procs.

Here is an example of the lines we still get in our logs:
[ActiveJob] [CacheWarmingJob] [7aafce65-1b3a-4183-bb44-ba447fb77cd1] Error performing CacheWarmingJob (Job ID: 7aafce65-1b3a-4183-bb44-ba447fb77cd1) from Sidekiq(low_priority) in 78.73ms: a before_perform callback halted the job execution

from activejob-uniqueness.

I should also call out that I know this is ActiveJob itself doing this - in fact I know the line of code is https://github.com/rails/rails/blob/13b3e7d83988d451ea305243319cc715a06617ea/activejob/lib/active_job/log_subscriber.rb#L93. But I was hoping there was an established wait to silence this would either a hacked logger or monkeypatching that subsciber.

from activejob-uniqueness.