Bitcoin full node and query server

Jul 27, 2020

View in context in the libbitcoin Slack #general mirror.

vdeurzen08:22
I believe I've also seen that on a first run while still syncing the chain, but certainly also after a restart
8 replies · evoskuil, vdeurzen · last Jul 27, 2020
evoskuil16:37
You’ve seen this many times but never reported it?
vdeurzen16:38
I've reported it several times, didn't pursue it any further because I needed a functional node more than I needed the latest version at the time
vdeurzen16:39
Note, I've seen it a couple of times not necessarily many times, but that is mainly due to the fact that after spending a bunch of time in GDB trying to figure out where it was going wrong I decided my time was better spent on getting my system working with v3
evoskuil17:04
Is there an open issue for it? I don’t recall ever seeing this, in v3 or v4, but would expect to see it if the store had been hard closed and restarted. It certainly could be the case though, since v4 has a lot of unverified work. The assertion that Amir is seeing is an possible indication of a consistency issue.
vdeurzen17:35
I didn't report an issue because within my time constraints I failed to narrow it down enough for a clear report. I was at the time unsure whether it was my own fault or a bug. Seeing it again I figured it would at least at credibility to know I had also seen it
evoskuil17:36
Ok, any error that doesn’t result from operating with a corrupted store is worth seeing.
vdeurzen17:38
If it happens to me again I'll make sure to make an issue on GH 👍
evoskuil17:38
Thx!