Closed sslotsky closed 9 years ago
My mistake here, it was not SuckerPunch but rather a websockets library that was causing the problem. Closing.
Nope, it's still SuckerPunch doing it.
It may be related to https://github.com/brandonhilkert/sucker_punch/pull/113
That seems likely! I will keep this open until that is merged and retest. Thanks!
v 1.5.0
has been released. Please try that version and see if you still have issues.
Closing since I haven't heard back.
@brandonhilkert Sorry I did not respond, this is indeed fixed. Thanks!
Great to hear. Thanks for the follow-up!
I recently introduced SuckerPunch to do some work that I was previously doing with DelayedJob. I was already using Celluloid actors & notifications successfully in my project to do some other processing. The newly wired SuckerPunch jobs work fine, but attempting to execute the code that uses notifications raises a
DeadActorError
with the message "notifications fanout actor not running"This error is raised as soon as I instantiate a subscriber:
This code is executed from the main thread in an ActiveRecord callback after a form is submitted. When I remove
SuckerPunch
from my project, the notifications work again.