Page MenuHomePhabricator

When an in-process worker subtask fails permanently, don't fatal the whole process
ClosedPublic

Authored by epriestley on Sep 8 2020, 8:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Feb 22 2024, 9:00 AM
Unknown Object (File)
Feb 20 2024, 8:29 AM
Unknown Object (File)
Jan 25 2024, 2:25 AM
Unknown Object (File)
Jan 16 2024, 9:03 PM
Unknown Object (File)
Dec 24 2023, 7:14 PM
Unknown Object (File)
Nov 30 2023, 4:28 AM
Unknown Object (File)
Nov 25 2023, 11:55 PM
Unknown Object (File)
Nov 17 2023, 9:08 AM
Subscribers
None

Details

Summary

Ref T13552. Fixes T13569. Currently, if a process uses in-process tasks (usually, a debugging/diagnostic workflow) and those tasks (or tasks those tasks queue) fail permanently, the exception escapes to top level and the process exits.

This isn't desirable; catch the exception and fail them locally instead.

Test Plan

With a failing Asana integration and misconfigured Webhook, ran bin/repository reparse --publish ....

  • Before: fatals on each substep.
  • After: warnings emitted for failed substep, but process completes.

Diff Detail

Repository
rP Phabricator
Branch
cref11
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 24884
Build 34332: Run Core Tests
Build 34331: arc lint + arc unit

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Sep 16 2020, 12:37 AM
This revision was automatically updated to reflect the committed changes.