Page MenuHomePhabricator

Make setCWD() with bad paths safer
ClosedPublic

Authored by epriestley on Apr 22 2016, 12:26 PM.
Tags
None
Referenced Files
F19511727: D15785.diff
Mon, Jan 12, 7:03 AM
F19507518: D15785.diff
Fri, Jan 9, 9:12 PM
F19205482: D15785.id38026.diff
Dec 16 2025, 8:04 PM
F18840424: D15785.id38026.diff
Oct 28 2025, 12:35 AM
F18822443: D15785.id.diff
Oct 23 2025, 6:44 AM
F18810166: D15785.id.diff
Oct 19 2025, 7:54 PM
F18770493: D15785.id38029.diff
Oct 8 2025, 12:55 PM
F18657225: D15785.diff
Sep 23 2025, 12:59 AM
Subscribers
None

Details

Summary

Ref T10853. This isn't a complete fix, but should prevent the most serious mistakes with setCWD() on bad paths.

Test Plan
  • Wrote a script using setCWD().
  • Gave it a bad path: got an explicit error.
  • Gave it a good path: things worked great.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make setCWD() with bad paths safer.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Apr 22 2016, 2:31 PM
This revision was automatically updated to reflect the committed changes.