-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix reorg - Create savepoint when close to tip and at max reorg depth #4169
Conversation
* this is useful as previously some times the first savepoint would have been the tip/really close to tip sometimes and if a reorg happened it could not restore at all and infinitely tried it
I'm going to have a look at this over the weekend. Could you check out if all the tests pass locally for you? CI seems to keep failing. |
Fixed tests. This should skip commiting for integ tests as it would require too long sleep duration for it to work. It passes all test slocally on my mac, I see on CI fails on ubuntu but I cannot reproduce this locally. |
Run the tests locally on an unbuntu env and it succeeds, probably something else happening in CI? |
Seems testnet4 has deep reorgs, https://testnet4.ordinals.com/status is unrecoverably reorged. If I am reading correctly the logs there was a reorg of 13 blocks deep, we should probably make configurable the savepoint interval? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
183c0bb
to
17ef2e2
Compare
I don't know why the CI doesn't pass |
Details
Create savepoint when close to tip and at max reorg depth
Context
This happened while trying to index testnet4(ord 22.1), and it indexes all the way to the tip (in my case 63038), then this happens:
Here are some additional logs I captured while debugging this
Tested
Indexed testnet 4 and it created the savepoint 21 blocks away from the tip