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
Looking at our NewRelic errors dashboard I notice quite a lot of exceptions that we don't see in Rollbar. Digging a bit deeper they are all raised from requests with non-existent paths that raise a RoutingError.
I'm not too familiar with how rails integrates with rack but to me this code looks intuitively wrong: env is supposed to be a hash and so that line should probably be:
@waltjones I dug a bit into it: We are still using Rails 4.2, and the signature of the render_exception method has changed in Rails 5.0: rails/rails@9503e65
Hi there,
Looking at our NewRelic errors dashboard I notice quite a lot of exceptions that we don't see in Rollbar. Digging a bit deeper they are all raised from requests with non-existent paths that raise a
RoutingError
.The relevant code is here: https://github.com/rollbar/rollbar-gem/blob/master/lib/rollbar/middleware/rails/show_exceptions.rb#L10
I'm not too familiar with how rails integrates with rack but to me this code looks intuitively wrong:
env
is supposed to be a hash and so that line should probably be:(The
to_s
call onkey
is also not necessary, sincekey
is always a String)Here is more context from NewRelic:
The text was updated successfully, but these errors were encountered: