Joshua Wood

Multiprocess windows (electrolysis) unsupported

12

In [about:support](about:support), the Multiprocess Windows option is disabled with any of the Arc themes active. When I switch back to the default Firefox theme Multiprocess Windows are enabled again. [Electrolysis](https://wiki.mozilla.org/Electrolysis)...

The default Ruby fingerprint is calculated server-side in our processing pipeline. Users can [customize the fingerprint](https://docs.honeybadger.io/lib/ruby/getting-started/customizing-error-grouping/) client-side using `before_notify` filter. This works fine for users who want to control grouping...

See https://github.com/rails/rails/pull/43625 Interface: ```ruby Rails.error.handle do 1 + '1' # raises TypeError end 1 + 1 # This will be executed Rails.error.record do 1 + '1' # raises TypeError end...

Initialize Honeybadger before Rails initializers

3

Idea: initialize Honeybadger before running other Rails initializers. In addition to catching more errors, this allows errors in initializers to be reported with the correct config (such as config.env, which...

Use Honeybadger logging.level setting when logging to Rails log

4

See #296 for additional context. Currently, the `logging.level` setting only works when `logging.path` (or a custom logger) is also configured. It would be nice if `logging.level` also applied to the...

While Rails [generally recommends](https://edgeguides.rubyonrails.org/active_job_basics.html#job-execution) that you don't use the default in-memory ActiveJob backend (async?) in production, it would be nice if we could support it for those who do.

Local/Nested Context

2

This feature would allow context to be set *only* for a block's execution: ```ruby Honeybadger.context({local: true}) do # Do stuff end ``` I took a stab at this in #229,...

Campaign testing approach

3

According to the [Rails testing guide](https://guides.rubyonrails.org/testing.html#testing-your-mailers): > The goals of testing your mailer classes are to ensure that: > > - emails are being processed (created and sent) > -...

Remove people from campaigns when they no longer match campaign segments

2

If they don't match campaign segments, they won't match any steps. Removing them early means that if they get re-added to a campaign once the *do* match again, they'll continue...

Delete user-orphaned campaign memberships in scheduler

2

Fixes #177 I was able to reproduce the error described in #177 by removing the `dependent: :delete_all` associations on the contact model + fixing an existing test to send the...