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
F15584351: D20649.id.diff
Thu, May 8, 3:02 AM
F15564583: D20649.id49262.diff
Wed, Apr 30, 12:57 PM
F15564264: D20649.id49262.diff
Wed, Apr 30, 11:17 AM
F15560196: D20649.id49261.diff
Tue, Apr 29, 1:24 PM
F15555215: D20649.id.diff
Mon, Apr 28, 10:23 AM
F15549649: D20649.diff
Sun, Apr 27, 7:06 AM
F15524900: D20649.diff
Mon, Apr 21, 11:07 AM
F15475184: D20649.id49261.diff
Apr 6 2025, 5:04 PM
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