[ 
https://issues.apache.org/jira/browse/THRIFT-1632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13403298#comment-13403298
 ] 

Nevo Hed commented on THRIFT-1632:
----------------------------------

Bryan,

Thanks for looking at this.  I definitely approached this from an outsider 
perspective looking at the two versions (C-ruby-lib vs ruby module) and 
attempted to make the broken one that does not seem to obliterate the data.

So my question is - is my change functionaly different than what is already in 
the ruby read_into_buffer() method? 
[lib/rb/lib/thrift/transport/memory_buffer_transport.rb]


                
> ruby: data corruption in thrift_native implementation of MemoryBufferTransport
> ------------------------------------------------------------------------------
>
>                 Key: THRIFT-1632
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1632
>             Project: Thrift
>          Issue Type: Bug
>          Components: Ruby - Library
>    Affects Versions: 0.7, 0.8, 0.9
>         Environment: Tested on Linux/Centos 6.0, with thrift_native.so 
> installed
>            Reporter: Nevo Hed
>            Assignee: Nevo Hed
>              Labels: newbie, patch
>         Attachments: patch, test.rb, test.thrift
>
>
> Detected a failure when serializing, then deserializing a specific object
> (I think the object needs to be large enough, AND probably must have non zero 
> data at a specific offset)
> $ /usr/bin/thrift --gen rb test.thrift && ruby test.rb 
> Caught Thrift::ProtocolException exception: Invalid value of field x1!
> Trace:
>   ./gen-rb/test_types.rb:34:in `validate'
>   test.rb:15:in `read'
>   test.rb:15

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to