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
When I configure rollbar with enable_rails_error_subscriber the details about the request is not sent. I can not see any data about this when viewing the error event. If I turn off enable_rails_error_subscriber the data is reported again.
I tested a little and with this modification I get the data again, not sure if this is the correct place to add it or if something more is missing.
The text was updated successfully, but these errors were encountered:
I've been seeing this problem too and, although I have applied a fix like @AlphonseSantoro (see above), which seemed to work when I tested it, I've just seen another error with no request info. 😞 Is there something missing from this fix? It's almost as if the request data is not available from the Rack environment...
Hi all, the rollbar-gem reporter can be updated to try to add these from the controller if it is present. I think there are a lot of cases though where the controller isn't passed to the report method.
When I tested this (at the time of the PR) there were many cases where the scope from the rollbar-gem middleware did have the request context, but the Rails reporter did not pass the controller, so the request context wasn't available there. If this were on the main thread, it would have the Rollbar scope set by the middleware regardless of the context param, but if I remember correctly, Rails calls the report method on a different thread.
When I configure rollbar with
enable_rails_error_subscriber
the details about the request is not sent. I can not see any data about this when viewing the error event. If I turn offenable_rails_error_subscriber
the data is reported again.I tested a little and with this modification I get the data again, not sure if this is the correct place to add it or if something more is missing.
The text was updated successfully, but these errors were encountered: