[
https://issues.apache.org/jira/browse/THRIFT-3746?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15231593#comment-15231593
]
ASF GitHub Bot commented on THRIFT-3746:
----------------------------------------
Github user nsuke commented on the pull request:
https://github.com/apache/thrift/pull/955#issuecomment-207199780
It seems that this change makes corss tests for Go server with JSON
protocol + Buffered transport flaky.
A normal RPC call right after oneway call sometimes fails to respond.
@tylertreat-wf do you have any idea how this happens ?
> JSON protocol left in incorrect state on read errors
> ----------------------------------------------------
>
> Key: THRIFT-3746
> URL: https://issues.apache.org/jira/browse/THRIFT-3746
> Project: Thrift
> Issue Type: Bug
> Components: Go - Library
> Reporter: Tyler Treat
> Assignee: Tyler Treat
> Fix For: 0.11.0
>
>
> This is related to THRIFT-3735, but the problem was not fully addressed
> there. The JSON protocol's read buffer needs to be reset to avoid being put
> in an invalid state on read errors.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
