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

Eric Mumau commented on MESOS-5904:
-----------------------------------

Cause:

Path:: dirname is used to parse the URL.  This error occurs in ProcessBase:: 
consume in mesos/3rdparty/libprocess/src/process.cpp at lines 3601 and 3603 (at 
the time of this comment).

 

Issue:

Path, defined in mesos/3rdparty/stout/include/stout/path.hpp, is an assortment 
of utilities for parsing a file path.  It is incorrectly used in this case to 
parse a URL path which is similar yet different from a file path.  The Path 
utilities use the constant variable os:: PATH_SEPARATOR as the delimiter for 
parsing paths.  os:: PATH_SEPARATOR is defined as '\\' for Windows builds and 
'/' for all other builds.  URL paths are not platform specific and use '/' as 
the delimiter.  The effect is that URLs are parsed incorrectly for Windows 
builds.  The Path utilities are not suitable for parsing URL paths.

> Process routes implementation seems to drop routes on Windows.
> --------------------------------------------------------------
>
>                 Key: MESOS-5904
>                 URL: https://issues.apache.org/jira/browse/MESOS-5904
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>            Reporter: Alex Clemmer
>            Assignee: Eric Mumau
>            Priority: Major
>              Labels: libprocess, mesosphere
>
> In several libprocess tests, the routes set up by process.cpp seem to be 
> getting mangled/dropped on Windows. Specifically:
> * HTTPTest.Endpoints help has the route '/help/(14)', but '/help/(14)/body' 
> fails; on HTTPTest.EndpointsHelpRemoval, the former can be removed, but when 
> the latter is attempted, it fails.
> * HTTPTest.NestedGet will properly generate the route '/a/b/c', but '/a/b' is 
> missing.
> * ProcessTest.FirewallDisabledPaths, FIrewallUninstall seem to fail to create 
> firewall rules.



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

Reply via email to