-
-
Notifications
You must be signed in to change notification settings - Fork 410
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
symbolize_key under JRuby #447
Comments
No special test case is required, testing under JRuby shows it:
Version 1.2 passes the tests. |
confirming the issue https://travis-ci.org/neo4jrb/neo4j/jobs/470657073 |
I suspect this is a bug in JRuby. Or at least a difference in how refinements are implemented there.
Thanks for including all the necessary steps to reproduce. It should be a straightforward fix.
I’m busy in the leadup to Christmas and probably won’t get to this myself until after Jan 2.
If you need a more urgent fix, I suggest submitting a PR yourself or reverting your app back to i18n 1.2.0.
…On 21 Dec 2018, 06:44 +1100, Heinrich Klobuczek ***@***.***>, wrote:
confirming the issue https://travis-ci.org/neo4jrb/neo4j/jobs/470657073
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
I have half fixed the issue today during a sliver of time I found: e88a260. However, there is yet another JRuby weirdness where it cannot find the method This will require at least an hour of my time to investigate and fix, which I will not have until after Jan 2. A patch in the meantime from someone more experienced with JRuby idiosyncrasies would be appreciated. |
Would you happen to know what development tools JRuby needs to install |
The issue is likely related to jruby/jruby#5054 or some other of many refinements-related issues jruby/jruby#5153. |
Can confirm this happening on jruby 9.2.4.0 and 9.2.5.0 with i18n 1.3.0 |
just upgraded to 1.3.0 and hit the issue. is there any hope for the PR to be merged soon ? 🙏 |
I’ll be dealing with this issue today. |
During the application startup, this line
results in an error:
What actually happened
Versions of i18n, rails, and anything else you think is neccessary
JRuby 9.2.5
Ruby 2.5.0
Rails 5.2.2
i18n 1.3.0
The text was updated successfully, but these errors were encountered: