You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 12, 2018. It is now read-only.
Unhandled errors in the routing table dispatcher fall through to default_errback (https://github.com/praekelt/vumi/blob/develop/vumi/dispatchers/endpoint_dispatchers.py#L56-L57). This logs the error and then acks the message to rabbit, causing the message to be marked and processed and logged. I propose that we implement a custom default_errback for the routing table dispatcher that logs the error and then re-raises it so that the message is not acked and returned to the Rabbit queue.
This is similar to what happened with the billing dispatcher recently (although that was addressed in a different way).
The text was updated successfully, but these errors were encountered:
Unhandled errors in the routing table dispatcher fall through to
default_errback
(https://github.com/praekelt/vumi/blob/develop/vumi/dispatchers/endpoint_dispatchers.py#L56-L57). This logs the error and then acks the message to rabbit, causing the message to be marked and processed and logged. I propose that we implement a customdefault_errback
for the routing table dispatcher that logs the error and then re-raises it so that the message is not acked and returned to the Rabbit queue.This is similar to what happened with the billing dispatcher recently (although that was addressed in a different way).
The text was updated successfully, but these errors were encountered: