curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randgalt <...@git.apache.org>
Subject [GitHub] curator pull request: [CURATOR-297] Handle quick close after start...
Date Tue, 02 Feb 2016 18:27:30 GMT
GitHub user Randgalt opened a pull request:

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

    [CURATOR-297] Handle quick close after start for PersistentNode

    Because start() creates the node async, if close is called immediately, it might occur
before the node creation. Handle this edge case by having the background response delete (async)
the node if the instance has been closed

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

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

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

    https://github.com/apache/curator/pull/130.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 #130
    
----
commit e5afda580e2c7540f5095e1894c6866ce4ace8db
Author: randgalt <randgalt@apache.org>
Date:   2016-02-02T18:26:13Z

    Because start() creates the node async, if close is called immediately, it might occur
before the node creation. Handle this edge case by having the background response delete (async)
the node if the instance has been closed

----


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