Page MenuHomePhabricator

In "bin/repository reparse", continue on "PhabricatorWorkerPermanentFailureException"
ClosedPublic

Authored by epriestley on Jun 18 2019, 3:02 PM.
Tags
None
Referenced Files
F18766284: D20588.id49106.diff
Tue, Oct 7, 3:55 PM
F18704456: D20588.id49107.diff
Sun, Sep 28, 7:41 AM
F18636384: D20588.diff
Sep 17 2025, 4:02 AM
F18570518: D20588.id49107.diff
Sep 10 2025, 3:27 AM
F18570517: D20588.id49106.diff
Sep 10 2025, 3:27 AM
F18567035: D20588.id.diff
Sep 9 2025, 3:28 PM
F18380645: D20588.diff
Aug 28 2025, 6:05 PM
F18380638: D20588.diff
Aug 28 2025, 6:05 PM
Subscribers
None

Details

Summary

Fixes T13315. See that task for discussion.

Without --background, we currently treat this as a catastrophic failure, but it's relatively routine for some repository states. We can safely continue reparsing other steps.

Test Plan

Ran bin/repository reparse --all X --message with commits faked to all be unreachable. Got warnings instead of a hard failure on first problem.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable