Page MenuHomePhabricator

Provide a more structured result log for Herald conditions
ClosedPublic

Authored by epriestley on Feb 17 2021, 9:48 PM.
Tags
None
Referenced Files
F17756254: D21563.id51353.diff
Tue, Jul 22, 1:53 PM
F17756253: D21563.id51334.diff
Tue, Jul 22, 1:52 PM
F17756033: D21563.id.diff
Tue, Jul 22, 1:33 PM
F17732063: D21563.diff
Sun, Jul 20, 3:52 AM
Unknown Object (File)
Jun 19 2025, 7:01 PM
Unknown Object (File)
Jun 4 2025, 7:15 PM
Unknown Object (File)
Jun 2 2025, 10:48 AM
Unknown Object (File)
May 10 2025, 8:05 AM
Subscribers
None

Details

Summary

Ref T13586. Currently, Herald condition logs encode "pass" or "fail" robustly, "forbidden" through a sort of awkward side channel, and can not properly encode "invalid" or "exception" outcomes.

Structure the condition log so results are represented unambiguously and all possible outcomes (pass, fail, forbidden, invalid, exception) are clearly encoded.

Test Plan

Screen Shot 2021-02-17 at 1.30.55 PM.png (755×1 px, 173 KB)

Screen Shot 2021-02-17 at 1.35.55 PM.png (705×1 px, 142 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable