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
F18819230: D21525.id51232.diff
Wed, Oct 22, 5:08 AM
F18643104: D21525.id.diff
Sep 19 2025, 1:31 AM
F18634990: D21525.id51234.diff
Sep 16 2025, 11:58 PM
F18571487: D21525.id51234.diff
Sep 10 2025, 5:04 AM
F18571484: D21525.id51232.diff
Sep 10 2025, 5:04 AM
F18105884: D21525.id51232.diff
Aug 10 2025, 8:17 PM
F18104229: D21525.id51234.diff
Aug 10 2025, 10:47 AM
F18102126: D21525.id.diff
Aug 9 2025, 6:25 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