-
Notifications
You must be signed in to change notification settings - Fork 115
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
uninitialized constant ActiveSupport::XmlMini::IsolatedExecutionState #851
Comments
We worked around this issue by explicitly installing older activesupport before krane in our dockerfiles:
Seems to work fine as a workaround, dunno if there are any fun side-effects. |
Pinning to v6 activesupport, since v7 causes krane to crash Shopify/krane#851
Pinning to v6 activesupport, since v7 causes krane to crash Shopify/krane#851
The blew up our updates as well. I consider it a critical issue because it breaks clean installs of |
I just want to voice my support for this. It broke our deployments after update of shipit-engine. krane is not usable with activesupport 7. |
Isn't #861 fixing this? |
@simi Indeed. Y'all just need to upgrade krane. This issue can be closed. |
Resolved by #861 |
Bug report
krane blows up on deploy since last night. Possibly related to Rails 7.0.0 release? See similar: rails/rails#43889
-> Need to require top level active_support in krane too? I'm not too familiar with Ruby or gem myself.
Expected behavior: krane doesnt blow up
Actual behavior: krane blows up
Version(s) affected: Both 2.3.0 & 2.3.4 are affected.
Steps to Reproduce
Run krane deploy:
The text was updated successfully, but these errors were encountered: