You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "David Reiss (JIRA)" <ji...@apache.org> on 2009/02/12 04:45:59 UTC
[jira] Commented: (THRIFT-340) TBinaryProtocol and
TBinaryProtocolAccelerated produce different values for at least the i64
type.
[ https://issues.apache.org/jira/browse/THRIFT-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12672867#action_12672867 ]
David Reiss commented on THRIFT-340:
------------------------------------
I can't reproduce this. If you can provide an example, that would be great.
> TBinaryProtocol and TBinaryProtocolAccelerated produce different values for at least the i64 type.
> --------------------------------------------------------------------------------------------------
>
> Key: THRIFT-340
> URL: https://issues.apache.org/jira/browse/THRIFT-340
> Project: Thrift
> Issue Type: Bug
> Components: Library (Python)
> Environment: FreeBSD 7
> Reporter: Jon Dugan
>
> TBinaryProtocol and TBinaryProtocolAccelerated produce different values for at least the i64 type.
> I don't have a nicely broken out example, but this is very easy to reproduce. I can generate an example if needed.
> This was true in the snapshot of the SVN repo from Jan 9, 2009. I checked recent commits and didn't see anything to address it.
> This appears to be very similar to THRIFT-313.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.