Rolf Wadstein

We have recently signed up for CodeClimate and are having the same issue. We recently were using HoundCi and with the switch to CodeClimate we are being forced to downgrade...

@maxjacobson Thank you for the info. Support had told me that last week and we addressed the issue on our side.. I should have come back to this issue in...

I can try to create a sample app that can represent our environment. It is possible that even the mechanism that a rails server reloads may have the same problem...

I managed to find some more detailed info as to why this is happening. It appears we have had this symptom for a long time, but it never got visibly...

Maybe the difference is with the different versions of Rails. We use 3.2.21. Specifically in 3.2.21, I managed to debug Rails and found it would validate whether it needs to...

Thank you and I greatly appreciate your input. I definitely agree we should not include modules if they are already included, so I will discuss with our platform team and...

@sergey-alekseev . It is true that it is not a memory leak. In development mode (or rather when `Rails.application.config.caches_classes = false`, the rake task reloads in the frequent scheduled intervals...

Actually, the rake task does not invoke that same code. Both rails middleware and DJ will call `prepare!`

But Rails middleware will run a block to update the @validated variable, where in DJ it does not. https://github.com/collectiveidea/delayed_job/blob/v4.0.6/lib/delayed/worker.rb#L296-L298 https://github.com/rails/rails/blob/857263445035404786e1f9785b76f3f4ddb7ca12/actionpack/lib/action_dispatch/middleware/reloader.rb#L68-L69

Since DJ is just calling the class method `ActionDispatch::Reloader.prepare!`, the `@validated` variable always defaults to `true` [here](https://github.com/rails/rails/blob/4-2-stable/actionpack/lib/action_dispatch/middleware/reloader.rb#L66).