Page MenuHomePhabricator

Make modular transforms handle exceptions gracefully
ClosedPublic

Authored by epriestley on May 12 2015, 3:20 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 10:18 PM
Unknown Object (File)
Tue, Dec 10, 3:31 AM
Unknown Object (File)
Sat, Dec 7, 7:22 PM
Unknown Object (File)
Wed, Dec 4, 2:10 AM
Unknown Object (File)
Tue, Dec 3, 11:20 AM
Unknown Object (File)
Thu, Nov 28, 5:39 PM
Unknown Object (File)
Wed, Nov 27, 6:25 PM
Unknown Object (File)
Wed, Nov 20, 4:35 PM
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.