Carson Reinke

I was able to reproduce the problem with the simple example (http://godrb.com) and with this configuration file: ``` ruby (1..20).each {|i| God.watch do |w| w.name = "simple#{i}" w.start = "ruby...

The problem appears to be `God::Driver` and the it's thread never empties `God::DriverEventQueue` (or something else I have not figured out). It is evident since there is no log entry...

I believe I found the issue, though I am not sure exactly why. Looking at [`God#control`](https://github.com/mojombo/god/blob/master/lib/god.rb#L471), it requests a stop before the unmonitor. So, when I updated `stop_all` to this,...

Looks like this might be favored now: https://github.com/svenfuchs/i18n-active_record

It does not, I believe it is related to [Process event exit](https://nodejs.org/api/process.html#process_event_exit). I was able to successfully fork and do some additional work.

Yes, just add this to an initializer: ``` ActiveJob::QueueAdapters::ResqueAdapter::JobWrapper.class_eval do extend Resque::Plugins::History end ```

Hello? @bookernath

@hanshuebner I tried this out and noticed the same thing. Any ID provided by the web interface is not usable. Instead, the only Album ID that is usable for this...

@tomdiggle this is a great idea, but having hard time with the "unused" identification process. I have been looking into this using `minimalcss`, but the problem is you need an...

@tomdiggle I think this is making an assumption that Sass is compiled on each request, I'm not positive, but pretty sure it is not. Unless BigCommerce would offer more information...