-
-
Notifications
You must be signed in to change notification settings - Fork 925
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
Jruby 9000 RC1 throws Java::JavaLang::ClassCastException: org.jruby.RubyBignum cannot be cast to org.jruby.RubyFixnum #3118
Labels
Milestone
Comments
Marked as beginner. We can fix quickly before 9k final, but someone else might want to try. |
@enebo, should this be retagged for a point release of JRuby 9.0.0.0? I don't think it was fixed for the first release. |
kares
added a commit
that referenced
this issue
Jul 30, 2015
Fixing ClassCastException reported in issue #3118
We should reopen this, after testing my case against jruby-head post merge against my own code base I get the following:
|
bigsur0
added a commit
to bigsur0/jruby
that referenced
this issue
Jul 31, 2015
With my previous commit, RangeError: bignum too big to convert into `long' was the result when running (0...2**64).max This commit ports handling for non-RubyFixnums from the 1.7.20 branch. Addresses, jruby#3118
bigsur0
pushed a commit
to bigsur0/jruby
that referenced
this issue
Jul 31, 2015
With my previous commit, RangeError: bignum too big to convert into `long' was the result when running (0...2**64).max This commit ports handling for non-RubyFixnums from the 1.7.20 branch. Addresses, jruby#3118
bigsur0
pushed a commit
to bigsur0/jruby
that referenced
this issue
Aug 4, 2015
With my previous commit, RangeError: bignum too big to convert into `long' was the result when running (0...2**64).max This commit ports handling for non-RubyFixnums from the 1.7.20 branch. Addresses, jruby#3118
eregon
pushed a commit
to ruby/spec
that referenced
this issue
Aug 28, 2015
Test issue reported in jruby/jruby#3118
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
VS.
The text was updated successfully, but these errors were encountered: