Bad valid-after time in 0.3.3 and 0.3.4
0.3.4 authorities will post votes that other authorities on 0.3.3 or 0.3.4 consider too old:
$ grep -r "21:05:33" . | grep -v -e info -e debug | sort -k 3
./000a/notice.log:Aug 29 21:05:33.786 [notice] Time to vote.
./000a/notice.log:Aug 29 21:05:33.790 [notice] Choosing valid-after time in vote as 2018-08-29 11:05:35: consensus_set=0, last_interval=5
./000a/notice.log:Aug 29 21:05:33.803 [notice] Vote posted.
./002aOLD/notice.log:Aug 29 21:05:33.811 [warn] Rejected vote from 127.0.0.1 ("Bad valid-after time").
./002aOLD/notice.log:Aug 29 21:05:33.811 [warn] Rejecting vote from 127.0.0.1 with valid-after time of 2018-08-29 11:05:35; we were expecting 2018-08-29 11:05:40
./003aOLD/notice.log:Aug 29 21:05:33.812 [warn] Rejected vote from 127.0.0.1 ("Bad valid-after time").
./003aOLD/notice.log:Aug 29 21:05:33.812 [warn] Rejecting vote from 127.0.0.1 with valid-after time of 2018-08-29 11:05:35; we were expecting 2018-08-29 11:05:40
./001a/notice.log:Aug 29 21:05:33.813 [warn] Rejected vote from 127.0.0.1 ("Bad valid-after time").
./001a/notice.log:Aug 29 21:05:33.813 [warn] Rejecting vote from 127.0.0.1 with valid-after time of 2018-08-29 11:05:35; we were expecting 2018-08-29 11:05:40
./000a/notice.log:Aug 29 21:05:33.815 [warn] http status 400 ("Bad valid-after time") response after uploading vote to dirserver '127.0.0.1:7002'. Please correct.
./000a/notice.log:Aug 29 21:05:33.818 [warn] http status 400 ("Bad valid-after time") response after uploading vote to dirserver '127.0.0.1:7003'. Please correct.
./000a/notice.log:Aug 29 21:05:33.820 [warn] http status 400 ("Bad valid-after time") response after uploading vote to dirserver '127.0.0.1:7001'. Please correct.
./000a/notice.log:Aug 29 21:05:33.835 [notice] Bootstrapped 80%: Connecting to the Tor network
But I've also seen 0.3.3 authorities reject their own votes for this reason.