Accumulator pattern delayed_action on fatal


#1

We recently get a situation usign accumulator pattern to manage our FW.

If you hit a fatal error (in our case a git resource could not reach the repository) before our rule resources are executed, FATAL will run queed delayed notifications (wich all templates on accumulator pattern uses through[1]) before re-raising exception to the main level and exits the program, so all accumulator templates are written to disk with incomplete variables.

That could potentially hit on a deny of service. Is there any way to avoid this? do we have to rescue all operations to watch the exceptions? That is not much dev friendly :S


#2

any tips?