You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Jake Farrell (JIRA)" <ji...@apache.org> on 2013/04/02 03:23:15 UTC
[jira] [Commented] (THRIFT-1911) IOError not being caught in
socket.rb
[ https://issues.apache.org/jira/browse/THRIFT-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619404#comment-13619404 ]
Jake Farrell commented on THRIFT-1911:
--------------------------------------
Andrew, Thanks for finding this issue, can you please submit a patch for this. Details on the process can be found at http://thrift.apache.org/docs/HowToContribute/
> IOError not being caught in socket.rb
> -------------------------------------
>
> Key: THRIFT-1911
> URL: https://issues.apache.org/jira/browse/THRIFT-1911
> Project: Thrift
> Issue Type: Bug
> Components: Ruby - Library
> Affects Versions: 0.9
> Reporter: Andrew Selder
>
> In Thrift::Socket#write at line 63, an IOError is raised if the socket is not open.
> However this raise is outside of the being/rescue block of the method, so this IOError propagates up instead of Thrift::TransportException. There is a rescue class that rescues StandardError and wraps in a TransportException, but is is not applied to this first line of the method.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira