curator-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From joelittlejohn <...@git.apache.org>
Subject [GitHub] curator pull request: Avoid erroneous 'Could not cancel' warning p...
Date Wed, 19 Mar 2014 15:48:22 GMT
GitHub user joelittlejohn opened a pull request:

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

    Avoid erroneous 'Could not cancel' warning produced by cache tasks

    When closing providers, we regularly see an erroneous warning related to a failure to
cancel cache tasks.
    
    This change applies some more defensive checks before attempting to cancel tasks, ensuring
that the cancel operation is only attempted if the future has not completed.

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

    $ git pull https://github.com/joelittlejohn/curator cancel-future-task

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

    https://github.com/apache/curator/pull/3.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 #3
    
----
commit 420ca78e252918e79ca5fe3e398d24f22b475b18
Author: Joe Littlejohn <joe.littlejohn@nokia.com>
Date:   2014-03-19T15:43:00Z

    Avoid erroneous 'Could not cancel' warning produced by cache tasks

----


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