-
-
Notifications
You must be signed in to change notification settings - Fork 408
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
[BUG] i18n 1.9.0 LoadError: cannot load such file -- i18n/core_ext/hash #603
Comments
Looks like there is a PR to revert the breaking change - #603 |
Right, #602 is the Pull Request. |
Meant #602 (not yet had coffee) 🤦🏻♂️ |
Actually this #573 (comment) might be the problem cause... |
I am sorry for stuffing this one up. Clearly #602 should've been merged and I should've looked at the right GH actions build, not the one before the latest. I've yanked 1.9.0, and have now pushed 1.9.1. |
The version 1.9.0 was yanked due to a bug: ruby-i18n/i18n#603
The version 1.9.0 was yanked due to a bug: ruby-i18n/i18n#603
Because v1.9.0 has been yanked. ruby-i18n/i18n#603 (comment)
Because v1.9.0 has been yanked. ruby-i18n/i18n#603 (comment)
For anyone using tools that give this error (e.g.
A potential fix is to create a file relative to a load path of the project (which may require forking it) at require 'active_support/core_ext/hash/keys' ... which will also require adding See: toptal/chewy#834 |
Because v1.9.0 has been yanked. ruby-i18n/i18n#603 (comment)
What I tried to do
See the CI run.
What I expected to happen
Passing tests.
What actually happened
An error in requires. https://github.com/ruby-i18n/i18n/search?q=core_ext shows that i18n/core_ext/hash is still being required, but is probably removed?
Versions of i18n, rails, and anything else you think is necessary
Affected: v1.9.0, which was just released.
Update: #602 makes CI green again.
Workaround is simple: in the Gemfile, avoid installing latest release.
See the CI output.
In addition, radar just did a greatly reduced the outstanding triage work on this repository. Kudos!
The text was updated successfully, but these errors were encountered: