thrift-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kenneth McFarland (JIRA)" <>
Subject [jira] [Commented] (THRIFT-4062) Remove debug print from TServiceClient
Date Fri, 17 Nov 2017 05:22:00 GMT


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:
>             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:
>     Remove debug print from TServiceClient
>     Client: Java
> You can merge this pull request into a Git repository by running:
>     $ git pull patch-1
> Alternatively you can review and apply these changes as the patch at:
> 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 <>
> 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 or file a JIRA ticket
> with INFRA.
> ---

This message was sent by Atlassian JIRA

View raw message