curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Randgalt <>
Subject [GitHub] curator pull request: [CURATOR-305] Async multi calls not returnin...
Date Wed, 02 Mar 2016 19:42:52 GMT
GitHub user Randgalt opened a pull request:

    [CURATOR-305] Async multi calls not returning error code

    CuratorTransactionImpl.makeCuratorResult() needs to check for ErrorResult and return it
in CuratorTransactionResult (new field probably needed).

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

    $ git pull CURATOR-305

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 #138
commit 5b1a7eaa72536cc6d489c3f9eab29fa568a86db6
Author: randgalt <>
Date:   2016-02-10T20:03:35Z

    [maven-release-plugin] prepare release apache-curator-3.1.0

commit a5bab5f49751a9a2e1096310cd86491e82ad91a9
Author: randgalt <>
Date:   2016-02-10T20:03:48Z

    [maven-release-plugin] prepare for next development iteration

commit 50550eecf0ad6cc677f92abd48f1de5c8875e689
Author: randgalt <>
Date:   2016-03-02T19:35:01Z

    Removed firstTime - I have no idea what it was supposed to do

commit 8ef32cc275f94a10576fc1a963d9f8db50ad382f
Author: randgalt <>
Date:   2016-03-02T19:41:31Z

    Expand CuratorTransactionResult to hold an error and include it in background multi calls


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.

View raw message