Closed AlexMohanMD closed 1 year ago
This should fix it. When I ran rails zeitwerk:check
before this commit, it failed. Running it after this commit passes it.
I am not sure why it wasn't caught when trying to just run the rails server in development as that usually finds all Zeitwerk errors like these.
can you update the gemfile.lock please @mickzijdel
Revert the revert!
@mickzijdel , the original PR broke delayed_job, referencing zeitwerk and kernel messages so I assume the host kernel is too old.
Please have a check :)