You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Andrew Schwartzmeyer (JIRA)" <ji...@apache.org> on 2018/02/09 00:16:00 UTC

[jira] [Commented] (MESOS-6838) Reconsider the semantics of `subprocess` on Windows

    [ https://issues.apache.org/jira/browse/MESOS-6838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16357741#comment-16357741 ] 

Andrew Schwartzmeyer commented on MESOS-6838:
---------------------------------------------

This issue will be resolved with https://reviews.apache.org/r/65574/ by fixing the TODO assertion.

> Reconsider the semantics of `subprocess` on Windows
> ---------------------------------------------------
>
>                 Key: MESOS-6838
>                 URL: https://issues.apache.org/jira/browse/MESOS-6838
>             Project: Mesos
>          Issue Type: Improvement
>          Components: libprocess
>            Reporter: Alex Clemmer
>            Assignee: Andrew Schwartzmeyer
>            Priority: Major
>              Labels: microsoft
>
> Right now, throughout the codebase, we are passing Windows shell commands into `subprocess`'s `argv` parameter, and ignoreing the `path` parameter. For example, we might do something like:
> {code}
> subprocess("", "cmd /c mesos-containerizer.exe", ...)
> {code}
> The `cmd /c` here is required. This obviously does not have high cohesion with the Unix usage of this, so we should consider ways to clean this up.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)