FWIW - It looks like the two shifts today where blocks were found may be missing some shares (though not nearly as bad as the shift probelm from yesterday). The crash when finding a block and the missing shares issue may be related. I thought you might want to know in case it helps narrow down the code you are looking at.
Yeah when I fix the 3 bad shifts I'll reset it back to before them and have it redo all the shifts since yesterday when it first happened.(It will also recalculate the rewards for these 2 blocks so they will be different, but for most people not much different)
In the ckdb crash that's happening now, one of the processing threads locks up when we find a block (it also says the cause so it's fixed in my testing code already)
Was just that at 2am I was real tired and decided to stop there and finish it in the morning
Oh well, it's morning now (almost 7am) better get to it once I'm a little more awake.
That of course doesn't affect anything except it caused a ckdb restart.