[
https://issues.apache.org/jira/browse/THRIFT-4062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16256497#comment-16256497
]
Kenneth McFarland commented on THRIFT-4062:
-------------------------------------------
This seems like uncharacteristic behaviour for an a Apache project.
This issue, based on demand, probably should have been fixed and pushed
over a month ago, given it only consist of removing a print statement. If
it's simple enough to ask users to patch then I believe the devs could do
it and push a release.
Frustrated users and projects will probably start looking for alternatives.
This can't be the most optimal resolution for Thrift or the downstream
projects that utilize it.
I want to believe there is a good reason for a lack of resolution but it
seems like an infinite redirect
> Remove debug print from TServiceClient
> --------------------------------------
>
> Key: THRIFT-4062
> URL: https://issues.apache.org/jira/browse/THRIFT-4062
> Project: Thrift
> Issue Type: Bug
> Components: Java - Library
> Affects Versions: 0.10.0
> Reporter: Jens Geyer
> Assignee: Tom Davis
> Priority: Critical
> Fix For: 0.11.0
>
>
> GitHub user tdavis opened a pull request:
> https://github.com/apache/thrift/pull/1173
> Remove debug print from TServiceClient
> Client: Java
> You can merge this pull request into a Git repository by running:
> $ git pull https://github.com/tdavis/thrift patch-1
> Alternatively you can review and apply these changes as the patch at:
> https://github.com/apache/thrift/pull/1173.patch
> To close this pull request, make a commit to your master/trunk branch
> with (at least) the following in the commit message:
> This closes #1173
>
> ----
> commit 670ad408b7f601798db7cf7b659ac231ba53c6a9
> Author: Tom Davis <[email protected]>
> Date: 2017-01-31T17:01:50Z
> Remove debug print from TServiceClient
>
> Client: Java
> ----
> ---
> If your project is set up for it, you can reply to this email and have your
> reply appear on GitHub as well. If your project does not have this feature
> enabled and wishes so, or if the feature is enabled but not working, please
> contact infrastructure at [email protected] or file a JIRA ticket
> with INFRA.
> ---
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
