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 2017/10/20 16:26:01 UTC
[jira] [Updated] (MESOS-8116) Fix off by-one error in Windows long
path support
[ https://issues.apache.org/jira/browse/MESOS-8116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Schwartzmeyer updated MESOS-8116:
----------------------------------------
Description: The NTFS long path patches have an off-by-one error, where the max path is actually exclusive, not inclusive. That is, a path at the internal max character limitation of 248 characters must also be prepended with '\\?\', not just paths > 248. So this amounts to switching a > to a >=, and writing some unit tests to prove it. (was: The NTFS long path patches have an off-by-one error, where the max path is actually exclusive, not inclusive. That is, a path at the internal max character limitation of 248 characters must also be prepended with {{\\?\}}, not just paths > 248. So this amounts to switching a > to a >=, and writing some unit tests to prove it.)
> Fix off by-one error in Windows long path support
> -------------------------------------------------
>
> Key: MESOS-8116
> URL: https://issues.apache.org/jira/browse/MESOS-8116
> Project: Mesos
> Issue Type: Bug
> Components: stout
> Environment: Windows 10
> Reporter: Andrew Schwartzmeyer
> Assignee: Andrew Schwartzmeyer
> Labels: windows
>
> The NTFS long path patches have an off-by-one error, where the max path is actually exclusive, not inclusive. That is, a path at the internal max character limitation of 248 characters must also be prepended with '\\?\', not just paths > 248. So this amounts to switching a > to a >=, and writing some unit tests to prove it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)