-
-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zeitwerk error under in Rails 7 / Ruby 3.1.2 #49
Comments
The issue might be a bit more complex actually. We are using a private gem that uses dry-monitor, but also, one of the dependencies use dry-monitor as well, so there is no need to require it and having it in gemspec at all (well, of course as long as this dependency uses dry-monitor). When we removed dry-monitor from gemspec , it fixed the issue. |
Thanks for reporting this. I think we need to configure zeitwerk to handle |
@Azdaroth I pushed 0.6.2 with a fix, please check it out |
@flash-gordon Thanks for submitting a fix! Now I'm getting |
uhm, this is supposed to be optional only when you want colorized SQL logging, I suspect that auto-loading is triggered in a way that ends up requiring the logging extension which depends on rouge 😞 |
I think we just need to opt-out extensions from autoloading, I'll take a look |
I pushed 0.6.3 with a fix |
@flash-gordon Thanks for the fix, everything looks fine now! |
Awesome |
Describe the bug
When running
bin/rails zeitwerk:check
I'm getting:Has anyone else experiences this issue?
My environment
The text was updated successfully, but these errors were encountered: