Tomohiko Mimura
Tomohiko Mimura
Oops, I missed that pull request. thanks π
> But the problem is Rollbar monkey patches everything to intercept errors, so it ends up in duplicate error reports: one from Rails ErrorSubscriber, and another from within Rollbar gem....
Thanks for the response π Yes, such an approach would be more flexible. However, we could not determine if it was the optimal solution π€ I have considered the use...
I just noticed that you already have the ability to customize a job class π (I don't know if this is an official config π) ```ruby Rails.application.config.after_initialize do # or...
Thanks. Yes, I agree. I think that will resolve this issue π
This may be due to the fact that SolidQueue was originally started by a Rake Task Rake Task is not `eager_load` by default. https://guides.rubyonrails.org/autoloading_and_reloading_constants.html#eager-loading However, if you start SolidQueue with...
In fact, one of the Rails products I know of that uses SolidQueue has a problem where constants cannot be referenced and errors βsometimesβ occur. It is frustrating that we...
Sorry for interrupting. After starting SolidQueue with the following settings, the constant reference error no longer occurs (SolidQueue version is v0.3.4, by the way). ```ruby config.rake_eager_load = true ``` My...