Closed olleolleolle closed 2 years ago
Looks like there is a PR to revert the breaking change - https://github.com/ruby-i18n/i18n/issues/603
Right, #602 is the Pull Request.
Meant #602 (not yet had coffee) 🤦🏻♂️
Actually this https://github.com/ruby-i18n/i18n/pull/573#issuecomment-1023621489 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.
For anyone using tools that give this error (e.g. chewy
v5)
LoadError: cannot load such file -- i18n/core_ext/hash
A potential fix is to create a file relative to a load path of the project (which may require forking it) at i18n/core_ext/hash.rb
and then have a single line in the file:
require 'active_support/core_ext/hash/keys'
... which will also require adding activesupport
as a dependency, if it wasn't already.
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!