Error handler context doesn't match docs

[darkhelmet]

Trying to get this working on our existing application with Rails 8.0.1 + Sidekiq

I wanted to log the errors so I started with the Rails.error stuff (first time using that as well). I subscribe and start logging to see what I want to keep track of:

class MaintenanceTasksErrorSubscriber
  def report(error, handled:, severity:, context:, source: nil)
    return unless source == 'maintenance_tasks'

    puts "Reporting error: #{error.class.name} - #{error.message}"
    puts "Handled: #{handled}"
    puts "Severity: #{severity}"
    puts "Context: #{context}"
    puts "Source: #{source}"
  end
end

Rails.error.subscribe(MaintenanceTasksErrorSubscriber.new)

The context has a single :job key which is the ActiveJob instance of MaintenanceTasks::TaskJob. The docs suggest the context is supposed to be a bunch of other stuff.

The source is also maintenance_tasks which is different from the docs as well.

Not sure if I'm doing something wrong to get these results, or if something else.

[darkhelmet]

The reason for doing what I was doing, is that I wanted to allow for multiple failures on a single run. It appears that if I report_on some errors it just sends them to reporting but doesn't track it on the run and display in the UI. It looks like that only supports a single error which then puts the run into a failed state. It would be swell to track multiple failures. I was going to try some Rails.cache shenanigans to tie all the data back to the run and then override a view to display it in the UI.

For example, I need to bulk update emails after an import, and they give me a spreadsheet of the emails we imported and what they should be updated to. But sometimes people have already updated their emails. Sometimes the email they want to use is already in use. I could silently ignore these failures to have the job succeed, but would be nice to have them displayed in the UI.