Page MenuHomePhabricator

Catch more HTTP VCS errors and convert them into VCS repsonses
ClosedPublic

Authored by epriestley on Jan 27 2021, 12:03 AM.
Tags
None
Referenced Files
F15450959: D21525.id51232.diff
Fri, Mar 28, 7:17 PM
F15449317: D21525.id51234.diff
Fri, Mar 28, 9:28 AM
F15446441: D21525.id.diff
Thu, Mar 27, 7:06 PM
F15441115: D21525.diff
Wed, Mar 26, 4:28 PM
F15440955: D21525.id51232.diff
Wed, Mar 26, 3:40 PM
F15419544: D21525.diff
Fri, Mar 21, 6:56 AM
F15346050: D21525.diff
Mon, Mar 10, 1:42 PM
F15287269: D21525.diff
Mar 4 2025, 7:43 PM
Subscribers
None

Details

Summary

Ref T13590. Currently, errors arising from cluster locking (like the "stuck write lock" exception) are not caught and converted into VCS responses on the HTTP VCS workflow.

Catch a broader range of exceptions and convert them into appropriate responses.

Test Plan
  • Forced a "stuck write lock" exception, pushed to a Git repository over HTTP.
  • Before: generic fatal.
  • After: VCS-specific fatal with a useful message in the "X-Phabricator-Message" response header.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable