Page MenuHomePhabricator

Explicitly pass PHABRICATOR_ENV and PHABRICATOR_INSTANCE to subprocesses

Authored by epriestley on Jan 5 2017, 10:33 PM.
Referenced Files
F12186576: D17148.diff
Sat, Sep 16, 11:04 PM
Wed, Sep 13, 6:32 AM
F12180971: D17148.diff
Tue, Sep 12, 4:00 PM
F12166790: D17148.diff
Thu, Sep 7, 1:59 AM
F12134788: D17148.diff
Aug 25 2023, 5:16 AM
Unknown Object (File)
Jul 24 2023, 4:52 PM
Unknown Object (File)
Jul 20 2023, 10:02 AM
Unknown Object (File)
Jul 19 2023, 5:37 PM



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

rPHU libphutil
Lint Not Applicable
Tests Not Applicable