You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/12/08 19:53:12 UTC
[jira] [Commented] (PROTON-765) 64-bit values are not being
properly marshalled in Ruby on 32-bit systems
[ https://issues.apache.org/jira/browse/PROTON-765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14238252#comment-14238252 ]
ASF subversion and git services commented on PROTON-765:
--------------------------------------------------------
Commit 2f8a70a3bcd1959ef3ef9bd6462aa60757d94c12 in qpid-proton's branch refs/heads/master from [~mcpierce]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=2f8a70a ]
PROTON-765: Fix Ruby's support for 64-bit values on 32-bit systems
Changed NUM2ULONG to NUM2ULL to properly use unsigned long long ints for
64-bit values.
> 64-bit values are not being properly marshalled in Ruby on 32-bit systems
> -------------------------------------------------------------------------
>
> Key: PROTON-765
> URL: https://issues.apache.org/jira/browse/PROTON-765
> Project: Qpid Proton
> Issue Type: Bug
> Components: ruby-binding
> Affects Versions: 0.8
> Reporter: Darryl L. Pierce
> Assignee: Darryl L. Pierce
> Fix For: 0.9
>
>
> On 32-bit Linux using both Ruby 1.8 and 2.0 I see the following when setting a Bignum value:
> 3: 2) A data object can hold a decimal64
> 3: Failure/Error: @data.decimal64 = value
> 3: RangeError:
> 3: bignum too big to convert into `unsigned long'
> 3: # ./lib/qpid_proton/data.rb:633:in `pn_data_put_decimal64'
> 3: # ./lib/qpid_proton/data.rb:633:in `decimal64='
> 3: # ./spec/qpid/proton/data_spec.rb:318:in `block (2 levels) in <module:Proton>'
> It seems that a >32-bit value can't be held on a 32-bit system in Proton.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)