ctpolicy permutes logs before submitting to them, to give each log a chance. The stagger feature was meant to sleep for an amount of time proportional to a log's position in the permuted list. However, it was actually using the log's position in the un-permuted list, so logs that appear later in the config would always be submitted to later than logs earlier in the config. This fixes that, and does some minor variable renaming for clarity. |
||
|---|---|---|
| .. | ||
| ctpolicy.go | ||
| ctpolicy_test.go | ||