Bump sentry-raven from 3.0.4 to 3.1.0
Bumps sentry-raven from 3.0.4 to 3.1.0.
Release notes
Sourced from sentry-raven's releases.
3.1.0
Feature
... (truncated)
Exclude all 4xx Rails errors (#1004)
See the full list here
Add some error context in
transport_failure_callback
(#1003)Before:
config.transport_failure_callback = lambda { |event| AdminMailer.email_admins("Oh god, it's on fire!", event).deliver_later }
After:
config.transport_failure_callback = lambda { |event, error| AdminMailer.email_admins("Oh god, it's on fire because #{error.message}!", event).deliver_later }
Support cleaning up exception backtrace with customized backtrace_cleaner (#1011)
The new config
backtrace_cleanup_callback
takes a lambda/proc object (default isnil
) and will be called with exception's backtraceRaven.configure do |config| config.backtrace_cleanup_callback = lambda do |backtrace| Rails.backtrace_cleaner.clean(backtrace) end end
And with the Rails integration, it'll automatically use a customized
Raven::Rails::BacktraceCleaner
to clean up exception's backtrace. It's basically Rails 6's backtrace cleaner but without silencers.The main reason to add this cleaner is to remove template methods from the trace, e.g.
app/views/welcome/view_error.html.erb in _app_views_welcome_view_error_html_erb__2807287320172182514_65600 at line 1
will become
app/views/welcome/view_error.html.erb at line 1
Changelog
Sourced from sentry-raven's changelog.
3.1.0
Feature
... (truncated)
Exclude all 4xx Rails errors (#1004)
See the full list here
Add some error context in
transport_failure_callback
(#1003)Before:
config.transport_failure_callback = lambda { |event| AdminMailer.email_admins("Oh god, it's on fire!", event).deliver_later }
After:
config.transport_failure_callback = lambda { |event, error| AdminMailer.email_admins("Oh god, it's on fire because #{error.message}!", event).deliver_later }
Support cleaning up exception backtrace with customized backtrace_cleaner (#1011)
The new config
backtrace_cleanup_callback
takes a lambda/proc object (default isnil
) and will be called with exception's backtraceRaven.configure do |config| config.backtrace_cleanup_callback = lambda do |backtrace| Rails.backtrace_cleaner.clean(backtrace) end end
And with the Rails integration, it'll automatically use a customized
Raven::Rails::BacktraceCleaner
to clean up exception's backtrace. It's basically Rails 6's backtrace cleaner but without silencers.The main reason to add this cleaner is to remove template methods from the trace, e.g.
app/views/welcome/view_error.html.erb in _app_views_welcome_view_error_html_erb__2807287320172182514_65600 at line 1
will become
app/views/welcome/view_error.html.erb at line 1
Commits
-
dfe16f1
release: 3.1.0 -
49e97d2
Fix changelog's format -
0cb173d
Revert "Update changelog for version 3.1.0" -
1f75f5c
Revert "Remove Unreleased header" -
78cc6e7
Remove Unreleased header -
a41c765
Update changelog for version 3.1.0 -
2b71009
Update CHANGELOG.md (#1028) -
f43c36c
Update CHANGELOG.md -
0ab5a47
Return value ofrescue_with_handler
when intercepting ActiveJob exceptions ... -
a5f101a
Revert rack-timeout deprecation (#1026) - Additional commits viewable in compare view