ApplicationCable::Connection has been removed from the module tree but is still active about anycable-rails HOT 11 CLOSED

For all interested, should be fixed in #85

from anycable-rails.

I see it too sometimes. It is most probably due to Rails code reloading in dev mode. Haven't investigated yet, but as a workaround you can alway restart RPC process in your process manager (would it be Overmind, Foreman, docker-compose or whatever):

overmind restart cable

docker-compose restart cable

from anycable-rails.

Could we keep the issue open until we understand what's wrong with the Executor middleware https://github.com/anycable/anycable-rails/blob/master/lib/anycable/rails/middlewares/executor.rb )?

Or I can create a new issue if the moderators prefer.

from anycable-rails.

Could we keep the issue open until we understand what's wrong with the Executor middleware

Agree.

from anycable-rails.

Janky, but worked around this for now by putting ApplicationCable::Connection in an non-autoloaded path.

from anycable-rails.

@bingjyang Can you show the way how you do it? Did you add ApplicationCable::Connection to autoloaded path explicitly before?

from anycable-rails.

I'm concerned because according to the default paths, ApplicationCable::Connection is outside of autoloading lookup.

https://github.com/rails/rails/blob/4aa6c328847bd42776f75befefbcc61cd1ec9f20/railties/lib/rails/engine/configuration.rb#L41-L65

from anycable-rails.

from anycable-rails.

Getting back to this... I suppose we followed the recommendation here and had it in app/channels/ (or maybe rails new auto-created it). Hence, it was being auto-loaded.

from anycable-rails.

Thank you!

from anycable-rails.

Closing since #85 has been released in 0.6.3

from anycable-rails.