#43 ResultsDB should not throw HTTP 500 on unknown state/outcome
Closed: Fixed Opened by jskladan.

At the moment, ResultsDB ends in Err500 for queries containing 'unknown' (as in not supported) values of state/outcome (e.g. http://taskotron-dev.fedoraproject.org/resultsdb_api/api/v1.0/results?outcome=UNKNOWN ). ResultsDB should return JSON structured error, and suitable HTTP state as in:
http://taskotron-dev.fedoraproject.org/resultsdb_api/api/v1.0/jobs/0


This ticket had assigned some Differential requests:
D367

Metadata