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
# @deprecated It will be removed in the next major release. Please read https://github.com/getsentry/sentry-ruby/issues/1522 for more information
38
-
# @return [Proc, nil]
39
-
attr_reader:async
40
-
41
34
# to send events in a non-blocking way, sentry-ruby has its own background worker
42
35
# by default, the worker holds a thread pool that has [the number of processors] threads
43
36
# but you can configure it with this configuration option
@@ -79,7 +72,6 @@ class Configuration
79
72
# @example
80
73
# config.before_send = lambda do |event, hint|
81
74
# # skip ZeroDivisionError exceptions
82
-
# # note: hint[:exception] would be a String if you use async callback
83
75
# if hint[:exception].is_a?(ZeroDivisionError)
84
76
# nil
85
77
# else
@@ -533,22 +525,6 @@ def release=(value)
533
525
@release=value
534
526
end
535
527
536
-
defasync=(value)
537
-
check_callable!("async",value)
538
-
539
-
log_warn<<~MSG
540
-
541
-
sentry-ruby now sends events asynchronously by default with its background worker (supported since 4.1.0).
542
-
The `config.async` callback has become redundant while continuing to cause issues.
543
-
(The problems of `async` are detailed in https://github.com/getsentry/sentry-ruby/issues/1522)
544
-
545
-
Therefore, we encourage you to remove it and let the background worker take care of async job sending.
546
-
It's deprecation is planned in the next major release (6.0), which is scheduled around the 3rd quarter of 2022.
0 commit comments