You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm seeing crashes when using this gem with rails 4.2.7.1 and it looks like the gem's process_action method gets called before (inside) the one from ActionController::Metal, so the event is not finished yet and tried to get its duration crashes with TypeError (can't convert nil into an exact number), because the @end ivar of the event is nil.
I'm using Puma as a web server and the exception happens in Rails production mode.
If you look at the stack trace below, it looks like ActionController::Metal::Instrumentation.process_action is called which calls this gems process_action method as its super method while still inside the ActiveSupport::Notifications.instrument("process_action.action_controller") block, so the event is not finished yet.
I think this might be a load order dependent problem, because all modules in ActionController get autoloaded, so this could probably be fixed by causing access to the constant in the ActiveSupport.on_load hook of the railtie.
I'm seeing crashes when using this gem with rails 4.2.7.1 and it looks like the gem's
process_action
method gets called before (inside) the one fromActionController::Metal
, so the event is not finished yet and tried to get its duration crashes withTypeError (can't convert nil into an exact number)
, because the@end
ivar of the event is nil.I'm using Puma as a web server and the exception happens in Rails production mode.
If you look at the stack trace below, it looks like
ActionController::Metal::Instrumentation.process_action
is called which calls this gemsprocess_action
method as its super method while still inside theActiveSupport::Notifications.instrument("process_action.action_controller")
block, so the event is not finished yet.I think this might be a load order dependent problem, because all modules in ActionController get autoloaded, so this could probably be fixed by causing access to the constant in the
ActiveSupport.on_load
hook of the railtie.The text was updated successfully, but these errors were encountered: