Sidekiq fails to start after Zeitwerk on docker dev

Tomorrow, I will work on one plugin so at the same time I will take a look on automatic reload :slight_smile:

4 Likes

@kris.kotlarek Any update on it? :smile:

1 Like

I only find out that Zeitwerk is not reloading engines code.
I found some answer here https://github.com/rails/rails/issues/35618
And on StackOverflow I found a recommendation to change back to :classic autoloader which is not our goal (How to reload helpers on rails mountable engine - Stack Overflow)
We will find out a way to reload engines, I will try to contact Zeitwerk authors for advice.

6 Likes

Hey! Just to clarify, in the preliminary WIP versions of Zeitwerk engines were loaded with a different loader, but that changed soon to be managed by the same loader of the application, and all is reloaded.

Can I help here in anyway?

5 Likes

I believe Kris has fixed most the issues we had, we will totally ping you if we are stuck on any issues, overall sailing has been pretty smooth! thanks so much for your work on Zeitwerk!!!

6 Likes