CT flaky submission failures #1084
Description
A signal boost that my PR creates some failed submissions due to safeSubmissionState not keeping state of the distinct operators when it setting the results. This causes a scenario where it submits two or three logs to a single operator and marks it as complete. This results in a violation of the Chrome policy which gets picked up after the fact and can be fully prevented.
I am currently working on a fix for it. Apologies for the bug.