Not a worry for this year, but potentially for next: the production fetch_and_publish_results.log can get quite large over time; after a few weeks of running continuously during 2018 testing, it got up to 1.4 GB in size. Maybe handle logging levels more conservatively for production, where disk size is limited and this could create a hard-to-debug issue on election nights?
Not a worry for this year, but potentially for next: the production
fetch_and_publish_results.logcan get quite large over time; after a few weeks of running continuously during 2018 testing, it got up to 1.4 GB in size. Maybe handle logging levels more conservatively for production, where disk size is limited and this could create a hard-to-debug issue on election nights?