checker/jobs, branch sigsumMoved to https://git.glasklar.is/glasklar/sigsum/admin/checkerhttps://getuid.sigsum.org/checker/atom?h=sigsum2022-07-22T05:42:49ZAllow for both list and string in sendEmail() to=2022-07-22T05:42:49ZLinus Nordberglinus@nordberg.se2022-07-22T05:38:37Zurn:sha1:27edd463b00f2f37a36f93eda62b2c6d8b0ca9a3Remove spurious backslash in message2022-07-22T05:42:09ZLinus Nordberglinus@nordberg.se2022-07-21T15:22:15Zurn:sha1:170dd84e7fe84ba0d364d5a6277454fa3de61bb6
I'm not sure if the initial backslash in '\From:' was on purpose or
not, but removing it makes at least my MUA a lot happier.
Another python3 fix, and some error logging2020-09-08T17:36:01ZTom Rittertom@ritter.vg2020-09-08T17:36:01Zurn:sha1:4b3658ff1fc7a9877552bd006fc09b5e25f83854Better error logging2020-09-08T17:35:45ZTom Rittertom@ritter.vg2020-09-08T17:35:45Zurn:sha1:9e24dfeaabd1c4daddb96c9c143f60cfa3374bf2Other python3 fixes2020-09-08T04:59:01ZTom Rittertom@ritter.vg2020-09-08T04:58:48Zurn:sha1:625f942d60c2f524f389f945a4e4743e57b9393ebase64 encode requires bytes2020-09-08T04:42:26ZTom Rittertom@ritter.vg2020-09-08T04:36:58Zurn:sha1:8aa8bab7f03e407556482304451f1e277c6285e7env python -> python32020-09-08T03:56:09ZTom Rittertom@ritter.vg2020-09-08T03:56:09Zurn:sha1:4f91d11b54a5008af7a76043035d0acbbff2392cRun futurize on the codebase for python32020-09-08T03:54:47ZTom Rittertom@ritter.vg2020-09-08T03:54:47Zurn:sha1:7deaed5205d0db6139f1c5e1f7c2b72181b1a208Correct line endings2020-09-08T03:52:47ZTom Rittertom@ritter.vg2020-09-08T03:52:47Zurn:sha1:4671e0dec5eab28941e598f109dbf77ed551a707Fix executions that stomped on each other2017-11-12T04:25:15ZTom Rittertom@ritter.vg2017-11-12T04:25:15Zurn:sha1:ee3eea047c10d0032efc5a8b98d9bbdb54fe0a3a
Every hour I would fire off two executions: the minute execution and the hour execution. Each would read the statefile on start.
Whichever execution took longer would overwrite the state file with the data that was present for the other's execution upon start.
This would manifest as extra notifications if the starts aligned - because the 'I already sent a notification' member update
wasn't being persisted.
This fixes it by only performing one execution at any given time, but knowing to run all the relevant jobs for that type of execution.
AKA When I run the hourly job I also run the minute jobs.
Another problem related to this one is logged in #1 - minute executions that take longer than a minute will also cause this type of error.