If Seer is configured with a consumer that wants to continue execution when encountering errors (a consumer that always returns true), it repeatedly reports the same error. This is because the unmodified EvalContext is pushed back on the stack in the main loop in the error case. This fixes the problem.
If Seer is configured with a consumer that wants to continue execution when encountering errors (a consumer that always returns
true
), it repeatedly reports the same error. This is because the unmodifiedEvalContext
is pushed back on the stack in the main loop in the error case. This fixes the problem.