GitHub user ahgittin opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/1160
Tasks cancellation
clearer semantics for cancel, and cancel dependent submitted tasks by
default
prevents leaks where dependent tasks (eg resolveValue) are submitted in the
background,
then the caller is cancelled; the interruption was not propagated. now by
default it is,
to children tasks and to submitted transients, with options for other
(weaker and stronger) cancellations.
see TaskInternal.cancel(TaskCancellationOptions), and new tests for
cancelling children in DynamicSequentialTaskTest.
also remove deprecated loose-typing ExecutionUtils.invoke,
more TRACE logging for activities,
and wrap batch config in a task so more resolutions are nested
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ahgittin/incubator-brooklyn tasks-cancellation
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/1160.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 #1160
----
commit 87ad37ae46644886adb7d99848a4802ee1559000
Author: Alex Heneveld <[email protected]>
Date: 2016-01-19T12:48:15Z
clearer semantics for cancel, and cancel dependent submitted tasks by
default
prevents leaks where dependent tasks (eg resolveValue) are submitted in the
background,
then the caller is cancelled; the interruption was not propagated. now by
default it is,
to children tasks and to submitted transients, with options for other
(weaker and stronger) cancellations.
see TaskInternal.cancel(TaskCancellationOptions), and new tests for
cancelling children in DynamicSequentialTaskTest.
also remove deprecated loose-typing ExecutionUtils.invoke,
more TRACE logging for activities,
and wrap batch config in a task so more resolutions are nested
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
