Adds a setup check which verifies that the XHPAST binary is built and up-to-date.
Details
- Reviewers
joshuaspence btrahan - Group Reviewers
Blessed Reviewers
- Deleted the XHPAST binary and saw the xhpast.binary setup issue.
- Built an older version of XHPAST and saw the xhpast.version setup issue.
- Built the latest version of XHPAST and saw no setup issues.
Diff Detail
- Repository
- rP Phabricator
- Branch
- arcpatch-D11514
- Lint
Lint Passed - Unit
Tests Passed - Build Status
Buildable 4272 Build 6135: [Placeholder Plan] Wait for 30 Seconds Build 4285: [Placeholder Plan] Wait for 30 Seconds
Event Timeline
I suspect the web user will frequently (or, frequently enough to cause support headaches) not have permission to perform the build, or GCC will not be installed, and I don't want new installs to explode when highlighting PHP code.
I'm hesitant to do this build from a web process at all because it may take significantly longer than all other setup/init sorts of checks (it takes a few seconds on my machine).
I'd accept a config warning about out-of-date / unbuilt XHPAST in Phabricator. It could maybe try to rebuild if the user presses a button to trigger it, but I don't want the autorebuild to occur by default. I also suspect the success rate will be low enough that this will frustrate users overall versus just giving them the command to run.
Rebase this on the static class and I can write some copy in the pull? The checks are good but I want to soften the language of the first one.
I want to rewrite the copy on this one but some stuff came up, let me just steal it for the moment.