You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "James Peach (JIRA)" <ji...@apache.org> on 2017/11/01 17:45:00 UTC
[jira] [Assigned] (MESOS-8155) subprocess clone argument should
return a Try
[ https://issues.apache.org/jira/browse/MESOS-8155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Peach reassigned MESOS-8155:
----------------------------------
Assignee: James Peach
> subprocess clone argument should return a Try<pid_t>
> ----------------------------------------------------
>
> Key: MESOS-8155
> URL: https://issues.apache.org/jira/browse/MESOS-8155
> Project: Mesos
> Issue Type: Bug
> Components: libprocess
> Reporter: James Peach
> Assignee: James Peach
>
> In libprocess, the {{subprocess}} API accepts a {{clone}} argument. This is supposed to return a {{pid_t}} and set {{errno}} on error. However. Mesos sometimes passes {{ns::clone}} as the {{clone}} argument, and this API does not set {{errno}} which results in {{subprocess}} propagating a misleading error message up the stack.
> Since it is not at all obvious how to map all the {{ns::clone}} error conditions to an expressive {{errno}}, we should just change the clone argument to return a {{Try<pid_t>}}.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)