Matthew Darwin

Let's keep an eye on it... ``` select date(from_unixtime(timestamp)) as date, hour(from_unixtime(timestamp)) as hour, count(*) from download_log where status = 591 group by date, hour having date > '2019-01-22'; +------------+------+----------+...

Definately better... ``` +------------+------+----------+ | date | hour | count(*) | +------------+------+----------+ | 2019-01-23 | 16 | 36 | | 2019-01-23 | 17 | 46 | | 2019-01-23 | 18...

Great thanks Peter. I look forward to the ongoing improvements. If you want to see what it looks like from my side at any time, feel free to check https://www.weatherstats.ca/debug/ec_dd_network_error.html...

Indeed the problem has returned. ``` +------------+------+----------+ | date | hour | count(*) | +------------+------+----------+ | 2019-01-26 | 0 | 2 | | 2019-01-26 | 1 | 2 | |...

No improvement... Since my last update, the numbers are: ``` | 2019-01-26 | 19 | 1 | | 2019-01-26 | 22 | 27 | | 2019-01-26 | 23 | 2024...

I assume the files are being written in an atomic fashion (write to a temp file and move the temp file into the desired final location) so that we aren't...

Yuck. This explains why there are duplicate forecast periods I get multiple times every day. Since you are writing a filter, then maybe you could filter those out too? eg...

@mikegabriel I don't use the sr download feature at all. I have a custom plugin so everything gets routed through to my own downloader so I can retry until I...

Today's download results (up to 23:15 EST): ``` MariaDB [weather]> select date(from_unixtime(timestamp)) as date, hour(from_unixtime(timestamp)) as hour, count(*) from download_log where status = 591 group by date, hour having date...

I don't think JSON object elements need to be returned in a consistent order so relying on that to be consistent seems like would be an error.