Page MenuHomePhabricator

Fix a bad call to "writeInfo()" in "bin/phd stop" with no PHABRICATOR_INSTANCE defined
ClosedPublic

Authored by epriestley on Jul 12 2019, 3:41 PM.
Tags
None
Referenced Files
F19694480: D20649.id49262.diff
Feb 10 2026, 10:09 AM
F19634064: D20649.diff
Feb 5 2026, 7:45 AM
F19469493: D20649.id49262.diff
Jan 4 2026, 11:46 PM
F19010755: D20649.diff
Nov 22 2025, 6:21 AM
F18599142: D20649.diff
Sep 13 2025, 6:47 AM
F18593625: D20649.id49261.diff
Sep 12 2025, 3:26 PM
F18567131: D20649.id.diff
Sep 9 2025, 3:32 PM
F18564399: D20649.id.diff
Sep 9 2025, 9:48 AM
Subscribers
None

Details

Summary
Test Plan
  • Purged PHABRICATOR_INSTANCE from my environment. In a Phacility development environment, it comes from loading services/.
  • Ran bin/phd stop with all daemons already stopped.
    • Before: bad call.
    • After: helpful error.
  • Ran some other bin/phd start, bin/phd status, etc., to kick the tires.
  • Grepped for remaining writeInfo() calls (found none).

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable