[
https://issues.apache.org/jira/browse/MESOS-5638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Mann updated MESOS-5638:
-----------------------------
Description: When registering callbacks with {{.then}}, {{.onAny}}, etc.,
we sometimes omit {{defer()}} in cases where it's deemed safe; for example,
when the callback uses no process state and thus could be executed in an
arbitrary context. Because of recent bugs due to the unsafe omission of
{{defer()}}, we should do a sweep of the codebase for all such occurrences and
evaluate their safety. We should also consider using {{defer()}} consistently
in all such cases, as our
[documentation|https://github.com/apache/mesos/tree/master/3rdparty/libprocess#defer]
recommends. (was: When registering callbacks with {{.then}}, {{.onAny}},
etc., we sometimes omit {{defer()}} in cases where it's deemed safe, either
because the . Because of recent bugs due to the unsafe omission of {{defer()}},
we should do a sweep of the codebase for all such occurrences and evaluate
their safety.)
> Check all omissions of 'defer' for safety
> -----------------------------------------
>
> Key: MESOS-5638
> URL: https://issues.apache.org/jira/browse/MESOS-5638
> Project: Mesos
> Issue Type: Bug
> Reporter: Greg Mann
> Labels: mesosphere
>
> When registering callbacks with {{.then}}, {{.onAny}}, etc., we sometimes
> omit {{defer()}} in cases where it's deemed safe; for example, when the
> callback uses no process state and thus could be executed in an arbitrary
> context. Because of recent bugs due to the unsafe omission of {{defer()}}, we
> should do a sweep of the codebase for all such occurrences and evaluate their
> safety. We should also consider using {{defer()}} consistently in all such
> cases, as our
> [documentation|https://github.com/apache/mesos/tree/master/3rdparty/libprocess#defer]
> recommends.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
