Page MenuHomePhabricator

Explicitly pass PHABRICATOR_ENV and PHABRICATOR_INSTANCE to subprocesses
ClosedPublic

Authored by epriestley on Jan 5 2017, 10:33 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jan 21, 11:05 AM
Unknown Object (File)
Wed, Jan 15, 3:46 AM
Unknown Object (File)
Dec 14 2024, 1:23 AM
Unknown Object (File)
Dec 13 2024, 4:28 PM
Unknown Object (File)
Dec 7 2024, 12:50 AM
Unknown Object (File)
Dec 4 2024, 10:54 PM
Unknown Object (File)
Nov 22 2024, 11:41 AM
Unknown Object (File)
Nov 18 2024, 1:22 PM
Subscribers
None

Details

Summary

Fixes T12070. Ref T12071. See T12071 for discussion.

D17100 changed things so that bin/repository gets an explicit TERM=dumb. As a side effect, this threw away the rest of the environment for installs with no "E" in variables_order. In particular, this means that "PHABRICATOR_ENV" may be dropped.

Since we're churning a lot and it's already Thursday, just patch this for now by reading "PHABRICATOR_ENV" out of the environment. I'll pursue more ambitious changes to fix this correctly after master promotes.

Test Plan
  • Patched Phabricator to log which PHABRICATOR_ENV it was reading to /tmp/env.log during startup.
  • Set variables_order to "GPCS" (no "E").
  • Ran PHABRICATOR_ENV=custom/porcupine ./bin/phd start.
    • Before patch: bin/repository subprocess lauched with no PHABRICATOR_ENV.
    • After patch: bin/repository subprocess gets PHABRICATOR_ENV correctly.

I also fiddled around with trying to fix this "right" without requiring config changes, but couldn't find or google anything that lets us rebuild $_ENV if variables_order is whack.

Diff Detail

Repository
rPHU libphutil
Lint
Lint Not Applicable
Unit
Tests Not Applicable