Mailing-List: contact dev-help@curator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@curator.apache.org
From: Randgalt <git@git.apache.org>
To: dev@curator.apache.org
Reply-To: dev@curator.apache.org
Message-ID: <git-pr-125-curator@git.apache.org>
Subject: [GitHub] curator pull request: [CURATOR-208] General fix for
 catch-alls thr...
Content-Type: text/plain
Date: Wed, 13 Jan 2016 20:22:46 +0000 (UTC)

GitHub user Randgalt opened a pull request:

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

    [CURATOR-208] General fix for catch-alls throughout the code and interruptes

    General fix for catch-alls throughout the code. This is overkill but it strikes me as the safest way to address the problem. Everywhere there is a catch-all add a check for InterruptedException and reset the thread's interrupted state

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/apache/curator CURATOR-208

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/curator/pull/125.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 #125
    
----
commit 003acc6027aa63e59b5de3b0d1da7e33c2b9f9cc
Author: randgalt <randgalt@apache.org>
Date:   2016-01-13T20:20:54Z

    General fix for catch-alls throughout the code. This is overkill but it strikes me as the safest way to address the problem. Everywhere there is a catch-all add a check for InterruptedException and reset the thread's interrupted state

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---