Page MenuHomePhabricator

Send the `aphlict` process log to the `node` log
ClosedPublic

Authored by epriestley on Apr 22 2016, 12:01 AM.
Tags
None
Referenced Files
F18751318: D15782.id38021.diff
Sat, Oct 4, 10:30 AM
F18659673: D15782.diff
Tue, Sep 23, 2:42 PM
F18621911: D15782.diff
Mon, Sep 15, 9:53 AM
F18620457: D15782.diff
Mon, Sep 15, 5:17 AM
F18202104: D15782.id38023.diff
Aug 18 2025, 9:21 AM
F18196721: D15782.id38022.diff
Aug 17 2025, 7:04 PM
F18194408: D15782.id.diff
Aug 17 2025, 9:53 AM
F18192273: D15782.id38021.diff
Aug 17 2025, 3:55 AM
Subscribers
None

Details

Summary

I've possibly seen a couple of aphlict processes exit under suspicious circumstances (maybe?). Make sure any PHP errors get captured into the log.

Test Plan
  • Added an exception after forking.
  • Before change: vanished into thin air.
  • After change: visible in the log.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Send the `aphlict` process log to the `node` log.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
  • Also print more diagnostic information about signals.
chad edited edge metadata.
This revision is now accepted and ready to land.Apr 22 2016, 12:43 AM
This revision was automatically updated to reflect the committed changes.