Closed westonganger closed 11 months ago
Im not currently using ActiveJob in my application so I would temporarily be ok to just disable this callback or disable litejob (not sure how to do either), however it would be alot better if it did not involve that.
Nevermind this ended up being an issue with system resources (I did something bad with Thread.new and wasnt cleaning up the threads after). It was just a coincidence that litejob was the last thing printed in all different scenarios. Sorry for the false-alarm.
Though I do think that maybe not printing the litejob messages at all when job count is 0 would be a good addition.
I am trying to deploy my application with capistrano. It used to work fine before switching to litestack.
Now the deployment just hangs/stops with the last lines being
What do we need to do to fix this.