-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Solidus breaking with Rails 5.2.2 #2989
Comments
Most likely related to #2978 |
@jacobherrington Maybe but I doubt it; the issue presented in #2978 failed from time to time (I'm assuming that's because of some random value being taken into consideration when seeding the database) while this one always fails. |
Could it be something related to the last Rails release happened yesterday? |
I thought so too @kennyadsl; maybe this one is more related to #2987? |
I don’t think it’s related since Ransack released a version that should fix that issue a couple of hours ago. |
@aitbw I see this now, I thought this was intermittent. This failure is new. |
I think it's related to some ActiveSupport deprecation change in latest Rails. I'd lock Rails support to 5.2.1 for now until we know what's going on. |
There are incompatibilities between core code and Rails 5.2.2 that we need to investigate better. Locking Rails to 5.2.1 should allow us to have all the ecosystem working in the meantime, for example this should immediately fix: - extensions tests against master - sandbox - heroku demo ref solidusio#2989
It seems like Adding a simple |
👍 where did you find that? I couldn't find any info about that in the ActiveSupport changelog |
Also, I don't think it's the only place where we are using |
Just my gut feeling 😊 |
Even with that alias added I get lots of strange method missing errors. Seems like something big (autoloading?) is screwed up in Rails 5.2.2 👎 |
I think it's related to this commit: rails/rails@015477a (related to rails/rails@a982a42) |
Closing via #2992 |
Steps to reproduce
bundle exec rake sandbox
on your Solidus source folderExpected behavior
Actual behavior
A "workaround" is available by commenting this line but doing so raises two (2) more errors:
and
System configuration
Extensions in use:
solidus_auth_devise
The text was updated successfully, but these errors were encountered: