You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@curator.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/11/08 05:07:00 UTC

[jira] [Commented] (CURATOR-438) Remove calls to MoreExecutors.sameThreadExecutor (deprecated)

    [ https://issues.apache.org/jira/browse/CURATOR-438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243384#comment-16243384 ] 

ASF GitHub Bot commented on CURATOR-438:
----------------------------------------

Github user asfgit closed the pull request at:

    https://github.com/apache/curator/pull/240


> Remove calls to MoreExecutors.sameThreadExecutor (deprecated)
> -------------------------------------------------------------
>
>                 Key: CURATOR-438
>                 URL: https://issues.apache.org/jira/browse/CURATOR-438
>             Project: Apache Curator
>          Issue Type: Improvement
>          Components: Apache
>         Environment: master branch
>            Reporter: Kenneth McFarland
>             Fix For: 4.0.1
>
>
> There are existing calls to MoreExecutors.sameThreadExecutor(), this issue has been opened and closed before. A quick look shows CURATOR-370, CURATOR-200 etc.. 
> While these other issues address the same problem, the patches did not remove all calls to the method so I took the liberty of doing it while getting familiar with the codebase.
> Please accept my humble first PR for Curator. Because this is my first PR I will let you know fyi that I have signed the ICLA.
> https://github.com/apache/curator/pull/240



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)