sentry-ruby 4.2.1 → 4.2.2

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 7cdabfd3ae3762fc2940760298daa15499a136d1cd71cca9f4e0bb64e30ee68e
-  data.tar.gz: 282e1a0bbfa3b45f5d4ecad1d8a30630e27b8d1eeb965a11eeaaf4dd110b70c6
+  metadata.gz: 2d155b5c7de2f02c985d3fb58851b865b912317effcb11575fcb0591162e476a
+  data.tar.gz: a021e74f77640a507c04c83476cdae19fc5938fba2ab02ddc2957e4c8abcc590
 SHA512:
-  metadata.gz: 259c3b62a98ff599bb79f836ccf161149e4fe63da5e186f1d596c8e511d2861aeb197e57b9c142abc89171f4366ea70d4a5d0c489b0ff7c7bd9b935656eadc96
-  data.tar.gz: 8d2feeec4eb23fd6fbf6090e7084494921365a3401a11ba5f6b5b8d9826d9199719bb80bbec1a048694cf1320fa9f389ce77969ff743320338645deb5b7f82c0
+  metadata.gz: 774ac5d839b028ee9889cce068cdde3dc8a5f34a32cb0db7582259ac805f4440003d188563bf00976a4a635bc3ef3610b746db63f298adca8600a682d3ab6f07
+  data.tar.gz: 3d29d303ab5c38cb0ea17d03c1e1e6287e5221fc4b34de33cdb21c2b3086ecafa60ba84112deb13f95af20d9966d91e6e1ff18800810b914b495fa3058b1df4b

data/README.md

@@ -26,7 +26,7 @@ The official Ruby-language client and integration layer for the [Sentry](https:/
 
 ## Requirements
 
-We test on Ruby 2.4, 2.5, 2.6 and 2.7 at the latest patchlevel/teeny version. We also support JRuby 9.0.
+We test on Ruby 2.4, 2.5, 2.6, 2.7, and 3.0 at the latest patchlevel/teeny version. We also support JRuby 9.0.
 
 If you use self-hosted Sentry, please also make sure its version is above `20.6.0`.
 
@@ -47,6 +47,7 @@ and depends on the integrations you want to have, you might also want to install
 ```ruby
 gem "sentry-rails"
 gem "sentry-sidekiq"
+gem "sentry-delayed_job"
 # and mores to come in the future!
 ```
 
@@ -136,6 +137,7 @@ We also provide integrations with popular frameworks/libraries with the related
 
 - [sentry-rails](https://github.com/getsentry/sentry-ruby/tree/master/sentry-rails)
 - [sentry-sidekiq](https://github.com/getsentry/sentry-ruby/tree/master/sentry-sidekiq)
+- [sentry-delayed_job](https://github.com/getsentry/sentry-ruby/tree/master/sentry-delayed_job)
 
 ### More configuration
 
@@ -143,38 +145,7 @@ You're all set - but there's a few more settings you may want to know about too!
 
 #### Blocking v.s. Non-blocking
 
-**Before version 4.1.0**, `sentry-ruby` sends every event immediately. But it can be configured to send asynchronously:
-
-```ruby
-config.async = lambda { |event, hint|
-  Thread.new { Sentry.send_event(event, hint) }
-}
-```
-
-Using a thread to send events will be adequate for truly parallel Ruby platforms such as JRuby, though the benefit on MRI/CRuby will be limited. If the async callback raises an exception, Sentry will attempt to send synchronously.
-
-Note that the naive example implementation has a major drawback - it can create an infinite number of threads. We recommend creating a background job, using your background job processor, that will send Sentry notifications in the background.
-
-```ruby
-config.async = lambda { |event, hint| SentryJob.perform_later(event, hint) }
-
-class SentryJob < ActiveJob::Base
-  queue_as :default
-  discard_on ActiveJob::DeserializationError # this will prevent infinite loop when there's an issue deserializing SentryJob
-
-  def perform(event, hint)
-    Sentry.send_event(event, hint)
-  end
-end
-```
-
-If you also use `sentry-rails`, you can directly use the job we defined for you:
-
-```ruby
-config.async = lambda { |event, hint| Sentry::SendEventJob.perform_later(event, hint) }
-```
-
-**After version 4.1.0**, `sentry-ruby` sends events asynchronously by default. The functionality works like this:
+`sentry-ruby` sends events asynchronously by default. The functionality works like this:
 
 1. When the SDK is initialized, a `Sentry::BackgroundWorker` will be initialized too.
 2. When an event is passed to `Client#capture_event`, instead of sending it directly with `Client#send_event`, we'll let the worker do it.
@@ -208,6 +179,21 @@ If you want to send a particular event immediately, you can use event hints to d
 Sentry.capture_message("send me now!", hint: { background: false })
 ```
 
+##### `config.async`
+
+You can also use `config.async` to send events with you own worker:
+
+```ruby
+config.async = lambda { |event, hint| SentryJob.perform_later(event, hint) }
+```
+
+And if you use `sentry-rails`, you can directly use the job we defined for you:
+
+```ruby
+config.async = lambda { |event, hint| Sentry::SendEventJob.perform_later(event, hint) }
+```
+
+
 #### Contexts
 
 In sentry-ruby, every event will inherit their contextual data from the current scope. So you can enrich the event's data by configuring the current scope like:

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: sentry-ruby
 version: !ruby/object:Gem::Version
-  version: 4.2.1
+  version: 4.2.2
 platform: ruby
 authors:
 - Sentry Team
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-02-09 00:00:00.000000000 Z
+date: 2021-02-18 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: sentry-ruby-core
@@ -16,14 +16,14 @@ dependencies:
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 4.2.1
+        version: 4.2.2
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 4.2.1
+        version: 4.2.2
 - !ruby/object:Gem::Dependency
   name: faraday
   requirement: !ruby/object:Gem::Requirement