Quote from: JRygh on August 04, 2017, 05:12:21 AM

Quote from: kano on August 04, 2017, 04:30:01 AM

There was also some failover/failback, at 04:23 UTC 4 minutes after the block, on the LA node of the 2 that handle stratum.kano.is (the other is Silicon Valley)
It affected about 20% of the miners on stratum.kano.is - with just a failover and an immediate failback.

I did not get reward for the last block. My miner has been online and running all the time. It was dropping hashrate during the failback, but why is the reward missing?

If you mean there's no rewards shown on the web site for 478946 yet?
Yeah it can sometimes take a while before kdb generates them.
It always does generate them, but the new code seems to delay it on occasion ... oh it did it just now ... 05:22:16 UTC

Edit: you can tell it hasn't done it yet coz the Blocks page still shows the "~" approximate stats.
Within a minute after it updates the block, and thus removes the "~"s, it generates the rewards.

Edit2: the processing order is: generate the shift that shows on the Shifts page first, then next update the block's statistics that shows that on the Blocks page by removing the "~", then lastly generate the rewards.

That step from 1 to 2 seems to take a long time sometimes, and yes I will look into again, at a later date, to see why there's a delay there, I didn't spot why with a quick look back when I first updated the DB code and the first new block also had the long delay of almost an hour.
I do know why it's supposed to be a bit slower, since I did write the code

, but I guess there's some unusual case where it can take almost an hour after the block, to decide to update the block's stats.