Drew Ulmer

Feel free to submit a PR.

The way to solve this problem with Motion right now is your option 3. It's possible that it's not the right choice at the moment based on the fact that...

@ernest4 one thing I've noticed can have an effect on startup time is your bootsnap cache. Especially if you've upgraded ruby versions without clearing it out. You can safely delete...

I've been on 1.3.1 of InheritedResources (the latest) for quite awhile and have had this problem ever since forever. It's kind of annoying, especially since my CanCan `current_ability` method is...

You can declare dependencies explicitly [very easily](https://github.com/rails/cache_digests#explicit-dependencies). The readme is pretty clear that it isn't intended to catch all versions of render and that you'll have to be explicit sometimes.

I guess I'm not sure. The easy fix is to be explicit. I can look into writing a fix but I'll defer to @dhh before spending time on it. My...

This still happens to me on Resque 2.5.0. I've had it about 9 times in the last month on Heroku.

All of my exceptions occur on the call to `@redis.pipelined` in `worker_done_working`: ``` [GEM_ROOT]/gems/resque-2.5.0/lib/resque/data_store.rb:293 :in `worker_done_working` [GEM_ROOT]/gems/resque-2.5.0/lib/resque/worker.rb:729 :in `done_working` ```

Hi @swombat 👋 Thanks for the bug report. I'm not 100% surprised that Motion isn't working well with Rails 7.1+. Unfortunately with the launch of Turbo/Hotwire as the blessed "Rails"...

This PR is still relevant, any chance of getting it merged? IDK if y'all accept contributions but it's a very short diff!