activeerror 1.0.0 → 1.0.1
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/README.md +3 -3
- data/app/models/active_error/fault.rb +2 -6
- data/lib/active_error/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 4a975ff9c639f582045df2fe349d69c5359b6060c0421f8c08e8c9e5a8578fcc
|
|
4
|
+
data.tar.gz: acbed4f63bd84ee096c225df7fbd693ed74586ae3813ca3c9c0b7e067ac5078d
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: b2d918aba97dea878b9f11e0bce25ea478c76ceb7aee9a479dcdb327c93aae3debde34af92e04cfc27ca8402993dd792e96782a770b21288809f0fe447bdf092
|
|
7
|
+
data.tar.gz: a82cd81c6b60217ac2a483d19e48f6ba02794b15028e0254e10a30b1e03a9f8304510c564a9d7a16e95bdc461e25f7d9c6994f5f089fb882ac36270244823c4c
|
data/README.md
CHANGED
|
@@ -2,8 +2,8 @@
|
|
|
2
2
|
|
|
3
3
|
One of the fundemental tools needed to take your Rails app to production is a
|
|
4
4
|
way to track errors that are triggered. Unfortunately, theres no free, easy,
|
|
5
|
-
open source way to track them for small or medium apps. Honeybadger
|
|
6
|
-
|
|
5
|
+
open source way to track them for small or medium apps. Honeybadger, Sentry,
|
|
6
|
+
and AppSignal are great, but they are are closed source. With Sentry
|
|
7
7
|
looking at using your data as training
|
|
8
8
|
data([link](https://blog.sentry.io/ai-privacy-and-terms-of-service-updates/?original_referrer=https%3A%2F%2Fsentry.io%2F))
|
|
9
9
|
there should be an easy open source alternative where you control the data.
|
|
@@ -16,7 +16,7 @@ with is the one baked into Rails that we use everyday in development. So with
|
|
|
16
16
|
ActiveError, when an error gets raised it's captured and stored in the
|
|
17
17
|
database (we attempt to group the same error together as Instances to reduce
|
|
18
18
|
noise) and then we recreate the error and display it using the built in debug
|
|
19
|
-
view from Rails. Once you've resolved the error you can click "Resolve"
|
|
19
|
+
view from Rails. Once you've resolved the error you can click "Resolve" which
|
|
20
20
|
will destroy the record.
|
|
21
21
|
|
|
22
22
|
|
|
@@ -13,15 +13,11 @@ module ActiveError
|
|
|
13
13
|
yaml: { unsafe_load: true }
|
|
14
14
|
|
|
15
15
|
serialize :backtrace, type: Array, coder: YAML
|
|
16
|
-
serialize :backtrace_locations, type: Array, coder: YAML,
|
|
16
|
+
serialize :backtrace_locations, type: Array, coder: YAML,
|
|
17
17
|
yaml: { unsafe_load: true }
|
|
18
18
|
serialize :blamed_files, type: Array, coder: YAML
|
|
19
19
|
|
|
20
|
-
scope :top_level,
|
|
21
|
-
left_joins(:parent_cause).where(
|
|
22
|
-
parent_causes_active_error_faults: { id: nil }
|
|
23
|
-
)
|
|
24
|
-
}
|
|
20
|
+
scope :top_level, -> { where.missing(:parent_cause) }
|
|
25
21
|
|
|
26
22
|
def exception
|
|
27
23
|
ExceptionMock.make(fault: self)
|
data/lib/active_error/version.rb
CHANGED