#275 Waiverdb consumer stops if error occurs
Merged by ralph. Opened by gnaponie.
gnaponie/greenwave nodecision-after-waiver  into  master

Download 275.patch

...and this is bad. Waiverdb consumer checks for each policy related if
there is a decision change and if it has to publish a message about it.
But if an error occurs during the decision (real life example: the
policy with the specified parameters does not exist) the consumer just
raises an exception and does not continue with the other policies.

:+1: we just did something similar like this in the resultsdb consumer, too.

Commit 8dc06a2a fixes this pull-request

Pull-Request has been merged by ralph

Pull-Request has been merged by ralph

Metadata