Page MenuHomePhabricator

Make modular transforms handle exceptions gracefully
ClosedPublic

Authored by epriestley on May 12 2015, 3:20 PM.
Tags
None
Referenced Files
F15537243: D12809.diff
Thu, Apr 24, 1:07 PM
F15472013: D12809.diff
Apr 5 2025, 10:36 AM
F15449580: D12809.id30828.diff
Mar 28 2025, 11:03 AM
F15448374: D12809.id30787.diff
Mar 28 2025, 4:30 AM
F15438875: D12809.id.diff
Mar 26 2025, 4:14 AM
F15436219: D12809.id30787.diff
Mar 25 2025, 12:43 PM
F15431910: D12809.diff
Mar 24 2025, 3:21 PM
F15409819: D12809.id30787.diff
Mar 19 2025, 5:31 AM
Subscribers

Details

Summary

Ref T7707. Ref T2479. Ref T5258.

The thumbnailing code is some of the only code in the codebase which doesn't use exceptions to handle errors. I'm going to convert it to use exceptions; make sure they do something reasonable at top level.

Strategy here is:

  • By default, we just fall back to a placeholder image if anything goes wrong.
  • Later, I'll likely add a "debug" workflow from the new "Transforms" UI which will surface the specific exception instead (the code can't really raise any interesting exceptions right now).
Test Plan

Faked an exception and saw some reasonable default images.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make modular transforms handle exceptions gracefully.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.May 12 2015, 6:26 PM
This revision was automatically updated to reflect the committed changes.