sentry-ruby 4.1.6 → 4.2.0

Sign up to get free protection for your applications and to get access to all the features.
Files changed (3) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +7 -1
  3. metadata +4 -4
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 449ea109c3ef382dba9e079a6f5a676be24fc4760a1cc2f62fc0cf1d54cf14bf
4
- data.tar.gz: 32b9ec5b1135d0307272e8593f2a7738836872e1a98e37667bf9e50be0799e37
3
+ metadata.gz: 4aa9700782e672548a16cd10395610a658bb73d37af363cd657f3f373c7118fe
4
+ data.tar.gz: 1995b50234b20e9a270fe35d7766dc0b816e6473723fe8d421278a04650257a5
5
5
  SHA512:
6
- metadata.gz: 2edbc3da5f78a2b04271b73698f021b9d5a80ce8bac2eddaebdad4d06609e8a3a8b068f0c18935a433d0442814645ad752ec9f7491c58169e9f8ec9735066497
7
- data.tar.gz: 21491f134004747589c23ec9c22995d543a22956dc313ace90d5f63652330a1e68da2bdbe146b449d1e924595a7f57be2eae739b7150f5cfee4e7eed0e1517b5
6
+ metadata.gz: b3856b5f92ba6a00cea9646c7aa18baa9739cd9f6472baef18f8bfae35db0c7047af98f2041e551382e2cff23505a00ba6c0da1cd7354e70b66c0e0d65bdf5e6
7
+ data.tar.gz: 44941a41ca3b8abd09b36a81fb7ebecc37cb4174092ae3bec5de96b2b0cc6e24830417933b374f8c91d4a32faf0838fc887c245a9080960f8c07e45166c976d0
data/README.md CHANGED
@@ -160,6 +160,7 @@ config.async = lambda { |event, hint| SentryJob.perform_later(event, hint) }
160
160
 
161
161
  class SentryJob < ActiveJob::Base
162
162
  queue_as :default
163
+ discard_on ActiveJob::DeserializationError # this will prevent infinite loop when there's an issue deserializing SentryJob
163
164
 
164
165
  def perform(event, hint)
165
166
  Sentry.send_event(event, hint)
@@ -167,8 +168,13 @@ class SentryJob < ActiveJob::Base
167
168
  end
168
169
  ```
169
170
 
171
+ If you also use `sentry-rails`, you can directly use the job we defined for you:
170
172
 
171
- **After version 4.1.0**, `sentry-ruby` sends events asynchronously by default. The functionality works like this:
173
+ ```ruby
174
+ config.async = lambda { |event, hint| Sentry::SendEventJob.perform_later(event, hint) }
175
+ ```
176
+
177
+ **After version 4.1.0**, `sentry-ruby` sends events asynchronously by default. The functionality works like this:
172
178
 
173
179
  1. When the SDK is initialized, a `Sentry::BackgroundWorker` will be initialized too.
174
180
  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.
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: sentry-ruby
3
3
  version: !ruby/object:Gem::Version
4
- version: 4.1.6
4
+ version: 4.2.0
5
5
  platform: ruby
6
6
  authors:
7
7
  - Sentry Team
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2021-02-02 00:00:00.000000000 Z
11
+ date: 2021-02-04 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: sentry-ruby-core
@@ -16,14 +16,14 @@ dependencies:
16
16
  requirements:
17
17
  - - '='
18
18
  - !ruby/object:Gem::Version
19
- version: 4.1.6
19
+ version: 4.2.0
20
20
  type: :runtime
21
21
  prerelease: false
22
22
  version_requirements: !ruby/object:Gem::Requirement
23
23
  requirements:
24
24
  - - '='
25
25
  - !ruby/object:Gem::Version
26
- version: 4.1.6
26
+ version: 4.2.0
27
27
  - !ruby/object:Gem::Dependency
28
28
  name: faraday
29
29
  requirement: !ruby/object:Gem::Requirement