forge_ops_tracker 0.10.1 → 0.10.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +4 -0
- data/README.md +21 -2
- data/lib/forge_ops_tracker/version.rb +1 -1
- metadata +4 -4
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 9b32a031e24fb613c219aee3bf01f0517043b05b4d1788d7ece456096d7561a0
|
|
4
|
+
data.tar.gz: 39c7f16920425d01862607b6d3f85b957c694ab009ce8ffd010f33714632a3a9
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 315fb4765179a298da43dd2beabe68970f257dee7b4b1f3938bcc6efa72ac403b8dbb0e39b8d16dfcaf19b76696aed961270dc88fd92731b05ae1610b3d4a223
|
|
7
|
+
data.tar.gz: f2907bae8015b4093346a30369cc3da38c8d36f4198ae4935cb1e2d2cea2e6baed44d5fcab4a8278029f228353d991275316fd54a9e08bd3116519b529f09159
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.10.2
|
|
4
|
+
|
|
5
|
+
- Documentation only: the README and package description now describe ForgeOps as a hosted service, link to getforgeops.net, and show the real host in the connection string example instead of a placeholder. No code changes.
|
|
6
|
+
|
|
3
7
|
## 0.10.1
|
|
4
8
|
|
|
5
9
|
- Sidekiq job failures now report the real error. Sidekiq raises its own control-flow exception
|
data/README.md
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
# ForgeOpsTracker
|
|
2
2
|
|
|
3
|
-
Rails exception reporting client for
|
|
3
|
+
Rails exception reporting client for [ForgeOps](https://getforgeops.net).
|
|
4
4
|
|
|
5
5
|
## Installation
|
|
6
6
|
|
|
@@ -15,7 +15,7 @@ Set a DSN (from a project's settings page in ForgeOps) via an initializer or env
|
|
|
15
15
|
```ruby
|
|
16
16
|
# config/initializers/forge_ops_tracker.rb
|
|
17
17
|
ForgeOpsTracker.configure do |config|
|
|
18
|
-
config.dsn = ENV["FORGE_OPS_DSN"] # "https://<api_key>@
|
|
18
|
+
config.dsn = ENV["FORGE_OPS_DSN"] # "https://<api_key>@getforgeops.net/api/v1/events"
|
|
19
19
|
config.release = ENV["HEROKU_SLUG_COMMIT"] || `git rev-parse HEAD`.strip
|
|
20
20
|
config.enabled_environments = %w[production staging] # default; reporting is a no-op elsewhere
|
|
21
21
|
end
|
|
@@ -67,6 +67,25 @@ Bottom line: if an exception would otherwise crash something, you're already cov
|
|
|
67
67
|
code already catches and handles it, route that specific `rescue` through `Rails.error.handle`/
|
|
68
68
|
`.record` instead of a bare one wherever you want ForgeOps to know about it.
|
|
69
69
|
|
|
70
|
+
### Sidekiq job failures and renamed job classes
|
|
71
|
+
|
|
72
|
+
A failing Sidekiq job is reported through `Rails.error` like any other error. Since 0.10.1 the issue
|
|
73
|
+
carries the real error, not Sidekiq's internal `Sidekiq::JobRetry::Handled` retry wrapper (which is
|
|
74
|
+
what every failing job used to arrive as, whatever went wrong inside it).
|
|
75
|
+
|
|
76
|
+
Renaming or removing a job class breaks every job still queued under the old name, since Sidekiq
|
|
77
|
+
stores the class name as a string, and no test can catch it because those jobs live in Redis. ForgeOps
|
|
78
|
+
recognizes that failure (an Active Job `UnknownJobClassError`, or a plain Sidekiq job's `NameError`
|
|
79
|
+
from constantizing the class), names the class that no longer exists, and shows how soon after which
|
|
80
|
+
release it first appeared. Keep the old name as an alias until the queue, retry set and scheduled set
|
|
81
|
+
have drained:
|
|
82
|
+
|
|
83
|
+
```ruby
|
|
84
|
+
# app/jobs/send_invoice_job.rb
|
|
85
|
+
# Kept only until jobs queued under the old name have drained, then delete this file.
|
|
86
|
+
SendInvoiceJob = DeliverInvoiceJob
|
|
87
|
+
```
|
|
88
|
+
|
|
70
89
|
## Identifying users
|
|
71
90
|
|
|
72
91
|
If you're using Devise, or any other Warden-based authentication, the currently signed-in user is
|
metadata
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: forge_ops_tracker
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 0.10.
|
|
4
|
+
version: 0.10.2
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- ForgeOps
|
|
@@ -79,8 +79,8 @@ dependencies:
|
|
|
79
79
|
- - "~>"
|
|
80
80
|
- !ruby/object:Gem::Version
|
|
81
81
|
version: '0.30'
|
|
82
|
-
description: Hooks Rails' error reporter and reports exceptions to
|
|
83
|
-
|
|
82
|
+
description: Hooks Rails' error reporter and reports exceptions to ForgeOps over HTTP,
|
|
83
|
+
without ever raising back into the host application.
|
|
84
84
|
executables: []
|
|
85
85
|
extensions: []
|
|
86
86
|
extra_rdoc_files: []
|
|
@@ -140,5 +140,5 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
140
140
|
requirements: []
|
|
141
141
|
rubygems_version: 4.0.11
|
|
142
142
|
specification_version: 4
|
|
143
|
-
summary: Rails exception reporting client for
|
|
143
|
+
summary: Rails exception reporting client for ForgeOps
|
|
144
144
|
test_files: []
|