curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bdumon <...@git.apache.org>
Subject [GitHub] curator pull request: CURATOR-157 Avoid stack traces on close
Date Thu, 30 Oct 2014 11:16:40 GMT
GitHub user bdumon opened a pull request:

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

    CURATOR-157 Avoid stack traces on close

    Avoid error-level stack traces closing PathChildrenCache followed by closing CuratorFramework
    
    See details in jira: https://issues.apache.org/jira/browse/CURATOR-157

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

    $ git pull https://github.com/bdumon/curator CURATOR-157

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

    https://github.com/apache/curator/pull/51.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 #51
    
----
commit 5ca022d2196f1b763043235fbdec439c1769fa9d
Author: Bruno Dumon <bruno@ngdata.com>
Date:   2014-10-30T11:05:51Z

    CURATOR-157 Avoid stack traces on close
    
    Avoid error-level stack traces closing PathChildrenCache followed by closing CuratorFramework

----


---
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.
---

Mime
View raw message