julewire-rails 1.1.2 → 1.1.3
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/docs/lifecycle.md +14 -0
- data/lib/julewire/rails/exception_severity.rb +1 -1
- data/lib/julewire/rails/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: 136f5154b76577b53e585c7eed30f1b98ad62241658418014b700df7a107cc94
|
|
4
|
+
data.tar.gz: f277e038bf9aa4b8133df286c9aa9e847dd290f58f89939a4b43a4229d385792
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f42e0904ef38c53f6e8d2048c2ff7f48c6c89fa48cc9defe2e9541fd5b6cc9c0437cb74264f29b224f87b76f94525661d025d763287251e98df4b194658ec0c1
|
|
7
|
+
data.tar.gz: 1675f80e9fda195311f4ddfcb8838ecc00ef66c905a24f0b2f4955d763abeac25354c539cbda7e3e7d1f0bd8a271136944b4aca73cf8733711f880c5db600e74
|
data/CHANGELOG.md
CHANGED
data/docs/lifecycle.md
CHANGED
|
@@ -11,6 +11,20 @@ It also registers a Rails `ActiveSupport::ForkTracker` after-fork hook that:
|
|
|
11
11
|
|
|
12
12
|
This covers Rails process forks that go through Rails' fork tracker.
|
|
13
13
|
|
|
14
|
+
Rails' tracker exposes only the after-fork side. A preloading process manager
|
|
15
|
+
that uses `julewire-ractor` must also quiesce Ractors before it forks. For Puma:
|
|
16
|
+
|
|
17
|
+
```ruby
|
|
18
|
+
before_fork { Julewire.before_fork! }
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Rails' fork tracker calls `Julewire.after_fork!` automatically in each child;
|
|
22
|
+
do not repeat it from Puma's `on_worker_boot` hook.
|
|
23
|
+
|
|
24
|
+
Stop application work before `before_fork`; do not create Ractors or emit from
|
|
25
|
+
other threads until the fork finishes. If the Puma master continues logging
|
|
26
|
+
between worker forks, call `Julewire.after_fork!` in its parent post-fork hook.
|
|
27
|
+
|
|
14
28
|
Custom destinations still own queue, retry, delivery, and reopen behavior. The
|
|
15
29
|
Rails hook only gives them lifecycle opportunities.
|
|
16
30
|
|