sentry-ruby 4.1.5 → 4.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: d5b6dac8f89a557f5c39b840cd9523355c96ba30bd9e713655bd7ebc2a3dcdf0
-  data.tar.gz: d779c5deb961ae968638e74c787284c35f81dcf65d35203fe66b01413c166f46
+  metadata.gz: 3f450d4675e2f6de879b83853aace0c6051ea680b35832da76a156b3a5d49fea
+  data.tar.gz: 392b363545f23cb65bc2b4a55afaab8767ad6a10f7f74b8d210b29218723dd79
 SHA512:
-  metadata.gz: 33516c955431dc91ab472d03917a2037af30682e4b2e7426621de98883ca7c5d92e4dd577163989caeecbf1c6e1a34cf92d2785d3305e660001614be451fb7da
-  data.tar.gz: 30f0e8aab4ff6fa6def5f062497bcb16c3c152580a9185e27bfc0ed4ac2bdd00bef4a0e79df7e92f0d82b5159bdef3d140b197e9e0b64799a67b6a06a0874c0d
+  metadata.gz: 98571bdbba234d79a982596afeb34549def742ad0f4a109af7f61c3d97ea49bddd6f7f65d099c59b6e40f97194f828161b62010216966b44dc3723c36a538543
+  data.tar.gz: c1e513dac483417242989841078adb5c674e7668518c95e1d7246f4b276650d5a45f11ae7f02e3250fbbb6cfc78e0bfdac08d8afb45ba8e59ec11dc409626b33

data/README.md

@@ -2,10 +2,14 @@
   <a href="https://sentry.io" target="_blank" align="center">
     <img src="https://sentry-brand.storage.googleapis.com/sentry-logo-black.png" width="280">
   </a>
-  <br>
+  <br />
 </p>
 
-# sentry-ruby, the Ruby Client for Sentry
+_Bad software is everywhere, and we're tired of it. Sentry is on a mission to help developers write better software faster, so we can get back to enjoying technology. If you want to join us [<kbd>**Check out our open positions**</kbd>](https://sentry.io/careers/)_
+
+Sentry SDK for Ruby
+===========
+
 
 **The old `sentry-raven` client has entered maintenance mode and was moved to [here](https://github.com/getsentry/sentry-ruby/tree/master/sentry-raven).**
 
@@ -26,7 +30,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 +51,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 +141,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,32 +149,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
-
-  def perform(event, hint)
-    Sentry.send_event(event, hint)
-  end
-end
-```
-
-
-**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.
@@ -202,6 +183,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.1.5
+  version: 4.3.0
 platform: ruby
 authors:
 - Sentry Team
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2021-01-27 00:00:00.000000000 Z
+date: 2021-03-12 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.1.5
+        version: 4.3.0
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - '='
       - !ruby/object:Gem::Version
-        version: 4.1.5
+        version: 4.3.0
 - !ruby/object:Gem::Dependency
   name: faraday
   requirement: !ruby/object:Gem::Requirement